Loading JPEG/Gif images causes Out Of Memory Error

Hello Java gurus, please shed some light on this.....
I am not a java newbie, but I am a java newbie in the area of dealing with graphics. I am using JDK 1.4.2_01 on Win XP with 2.4ghz and 512 RAM. When I try to read in a (or a few) JPEG image into a JLabel using ImageIcon, I get an out of memory error everytime. This happens whether I am reading the image out of a jar file or out of a local directory. The JPEG's are 8.5" x 11", and range between 150kb to 900kb. I am trying to load approximately 10 images in a JTabbedPane using new JLabel(ImageIcon) on individual JPanels (one JPanel for each JPEG). Now I get the java.lang.outofmemory error whether I try to load 1 image or 10 images. Anyone got a clue as to what I am doing wrong? I actually do get one image loaded before the error gets thrown. So I do know that it is trying to load the right image. What is going on here? Is it an ImageIcon problem, or are there others who have run into this. It has brought this project to a grinding halt, and I had thought this would be the easier part!!!! Please help me out gurus! Thanks!

What options/values are you suggesting that I set? Or do you mean something else? Thank you for any ideas that can help me solve this problem. I never had any issues dealing with using ImageIcon for toolbar button graphics (file sizes of 1-3kb), but now with dealing with full page graphics I have run into a brick wall with this out of memory error.

Similar Messages

  • Scaling images and Out of memory error

    Hi all,
    Does anyone knows why this code throws an out of memory error?
    It loads an image (2048x1166 pixels) and saves it at bufi1 (BufferedImage). After that:
    1- Rescale bufi1 to bufi13A (x3).
    2. Rescale bufi1 to bufi12 (x2).
    3. Rescale bufi1 to bufi13B (x3).
    At 3, the code throws an oome. Why?
    Thanks in advance!
    import java.io.*;
    import javax.imageio.*;
    import java.awt.geom.*;
    import java.awt.image.*;
    public class TestScalePercent {
      public static void main(String[] args) {
        TestScalePercent tsp=new TestScalePercent();
        BufferedImage bufi1=null;
        try {
          bufi1 = ImageIO.read(new File("foo.png"));//2048x1166 pixels
        } catch (Exception e){
          e.printStackTrace();
        BufferedImage bufi13A=tsp.scale(bufi1,3,3);//--> OK
        BufferedImage bufi12=tsp.scale(bufi1,2,2);//--> OK
        BufferedImage bufi13B=tsp.scale(bufi1,3,3);//-->OOM error!
      public BufferedImage scale(BufferedImage bufiSource, double scaleX, double scaleY){
        AffineTransform tx = new AffineTransform();
        tx.scale(scaleX,scaleY);
        AffineTransformOp op = new AffineTransformOp(tx, AffineTransformOp.TYPE_NEAREST_NEIGHBOR);
        BufferedImage bufiop=op.filter(bufiSource, null);//--> Creates the OOM error...
        return op.filter(bufiop, null);
    }

    How much memory does your machine have?
    That image is quite large. If my math is correct and
    assuming the image has 32-bit color the original
    image takes up 76.5 megs of memory by itself. Then
    you are trying to create three other versions of it.
    It isn't lying to you, it is indeed probably running
    out of memory to hold the images.OK. Now I'm wondering if is it possible to free memory between bufi13A - bufi12, and bufi12 - bufi13B? I've tried to invocate the garbbage collector but nothing happens...
    Thanks!

  • Data merge with football tickets. Printing causes out of memory errors. Can only print 10 at a time!

    Here's the deal. Printing football tickets for the local high school. 10 tickets per 8.5 x 11 sheet. All black and white. I couldn't data merge into one whole document of tickets because it was failing to do that. So, I end up with 3 documents. First two have 50 pages of tickets and the last has 37 pages.
    When I go to print, I can only print 10 pages at a time or InDesign straight up crashes or I get an "Out of Memory" error which is bull because I've got plenty of ram available (unless it's complaining about lack of HD space for some reason)
    Incredibly frustrating.
    Each ticket has 3 images on it. Two of the images are the same. Those two images are about 103kb .ai files. Very very simple. The other image is a TIFF that is about 76kb. So there are 1000 .ai files / document and 500 TIFFs.
    Here's a video I took of it ripping: http://www.youtube.com/watch?v=UCjvdmXuaYs&feature=c4-overview&list=UUf_1UFp80YLZJfCyIxXEg kg
    Also, when printing, I have the Send Data set to Optimized Subsampling instead of "All". That's not seeming to help.
    Any thoughts?
    IDCS 5.5
    OSX 10.8.4

    I just ran a sample on my laptop.
    AI file, duplicated, is 284k. Image is roughly 200k. The CSV has 2054 records, and the merged document with 10 per page is 250 megabytes. PDF is just under 50 megs.
    This laptop has only 4 gigs memory but has a lot of free disk space. It took a good amount of time to do the merge, a bit longer to create the PDF-X1a PDF.
    Mike

  • Displaying Large Images and Out of Memory Error

    hi,
    I am relatively new to JAVA and I have been trying to display a large jpeg in a scrollpane. The image is about 30 mb in size and is very long. When compressed the image is very small (1mb) but when uncompressed it increases in size due to the black background. I have been looking all over the place to find a method to display such a large image. I read a little bit about the JAI and its tile features but I am not really familiar with it. Also the image has to be displayed in an applet. the whole mess has to do with the JAVA VM memory restrictions as it does not have enough memory to process the image. Is there a way to uncompress a part of the JPEG and display it or assign addittional memory to JAVA. I will really appreciate any help on this topic.
    thanks

    Hiya.
    I can't say I know how to save Java from large images, but you can up the memory allocated to the JVM:
    java -Xmx120M ...
    will give 120M to the JVM (max). There is an -Xms also which gives the initial allowed space.
    Regards.
    Paulj.

  • Korg Legacy collection is what causes Out of Memory error

    Hi guys
    I'm pretty sure i've narrowed it down to this. I don't seem to get it unless i've got a few instances of it. Anyone able to offer advise/confirm/comment?
    Thanks guys
    Eddie

    Being a rompler, the legacy coll. is a RAM hog. Try using it in multimode to save memory. It should have a "dump unused samples" feature, but it doesn't

  • (AIR) out of memory error when building workspace

    Hi,
    I created a very simple AIR project. But during the load the
    workbench gave me out of memory errors.
    Please find below the relevant .log entries.
    Thanks for your help,
    -Rogier
    !SESSION 2007-06-13 14:13:10.241
    eclipse.buildId=unknown
    java.version=1.5.0_11
    java.vendor=Sun Microsystems Inc.
    BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
    Command-line arguments: -os win32 -ws win32 -arch x86
    !ENTRY org.eclipse.ui 4 4 2007-06-13 14:13:30.383
    !MESSAGE Invalid Menu Extension (Path is invalid):
    goToResource
    !ENTRY org.eclipse.ui 4 4 2007-06-13 14:13:46.565
    !MESSAGE Invalid Menu Extension (Path is invalid):
    org.eclipse.jdt.ui.actions.GoToPackage
    !ENTRY org.eclipse.ui 4 4 2007-06-13 14:13:46.565
    !MESSAGE Invalid Menu Extension (Path is invalid):
    org.eclipse.jdt.ui.actions.GoToType
    !ENTRY org.eclipse.core.jobs 4 2 2007-06-13 16:29:02.002
    !MESSAGE An internal error occurred during: "Building
    workspace".
    !STACK 0
    java.lang.OutOfMemoryError: PermGen space
    !ENTRY org.eclipse.ui 4 4 2007-06-13 16:29:02.159
    !MESSAGE Unhandled event loop exception
    !ENTRY org.eclipse.ui 4 0 2007-06-13 16:29:02.159
    !MESSAGE PermGen space
    !STACK 0
    java.lang.OutOfMemoryError: PermGen space
    !ENTRY org.eclipse.core.jobs 4 2 2007-06-13 16:29:04.675
    !MESSAGE An internal error occurred during: "Building
    workspace".
    !STACK 0
    java.lang.OutOfMemoryError: PermGen space
    !ENTRY org.eclipse.ui 4 4 2007-06-13 16:29:04.691
    !MESSAGE Unhandled event loop exception
    !ENTRY org.eclipse.ui 4 0 2007-06-13 16:29:04.691
    !MESSAGE PermGen space
    !STACK 0
    java.lang.OutOfMemoryError: PermGen space
    !ENTRY org.eclipse.ui 4 4 2007-06-13 16:29:19.067
    !MESSAGE Unhandled event loop exception
    !ENTRY org.eclipse.ui 4 0 2007-06-13 16:29:19.098
    !MESSAGE Failed to execute runnable
    (java.lang.OutOfMemoryError: PermGen space)
    !STACK 0
    org.eclipse.swt.SWTException: Failed to execute runnable
    (java.lang.OutOfMemoryError: PermGen space)
    at org.eclipse.swt.SWT.error(SWT.java:3374)
    at org.eclipse.swt.SWT.error(SWT.java:3297)
    at
    org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:126)
    at
    org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
    at
    org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
    at
    org.eclipse.jface.window.Window.runEventLoop(Window.java:820)
    at org.eclipse.jface.window.Window.open(Window.java:796)
    at
    org.eclipse.ui.internal.ide.dialogs.InternalErrorDialog.open(InternalErrorDialog.java:78)
    at
    org.eclipse.ui.internal.ide.dialogs.InternalErrorDialog.openQuestion(InternalErrorDialog. java:185)
    at
    org.eclipse.ui.internal.ide.IDEExceptionHandler.openQuestionDialog(IDEExceptionHandler.ja va:174)
    at
    org.eclipse.ui.internal.ide.IDEExceptionHandler.handleException(IDEExceptionHandler.java: 100)
    at
    org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor.eventLoopException(IDEWorkbenchAdvisor.ja va:298)
    at
    org.eclipse.ui.internal.ExceptionHandler.handleException(ExceptionHandler.java:62)
    at
    org.eclipse.ui.internal.progress.ErrorNotificationManager$1.run(ErrorNotificationManager. java:82)
    at
    org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    at
    org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123)
    at
    org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3325)
    at
    org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2971)
    at
    org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
    at
    org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
    at
    org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
    at
    org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at
    com.adobe.flexbuilder.standalone.FlexBuilderApplication.run(FlexBuilderApplication.java:1 03)
    at
    org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
    at
    org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:92)
    at
    org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:68)
    at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
    Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
    Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at
    org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
    at org.eclipse.core.launcher.Main.run(Main.java:977)
    at org.eclipse.core.launcher.Main.main(Main.java:952)
    Caused by: java.lang.OutOfMemoryError: PermGen space
    !ENTRY org.eclipse.ui.workbench 4 2 2007-06-13 16:34:11.522
    !MESSAGE Problems occurred when invoking code from plug-in:
    "org.eclipse.ui.workbench".
    !STACK 0
    java.lang.NullPointerException
    at
    org.eclipse.ui.internal.EditorManager.convertToSaveables(EditorManager.java:1336)
    at
    org.eclipse.ui.internal.EditorManager.saveAll(EditorManager.java:1203)
    at
    org.eclipse.ui.internal.Workbench$13.run(Workbench.java:790)
    at
    org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:37)
    at
    org.eclipse.ui.internal.Workbench.saveAllEditors(Workbench.java:738)
    at
    org.eclipse.ui.internal.Workbench.busyClose(Workbench.java:658)
    at
    org.eclipse.ui.internal.Workbench.access$8(Workbench.java:642)
    at
    org.eclipse.ui.internal.Workbench$15.run(Workbench.java:855)
    at
    org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:67)
    at
    org.eclipse.ui.internal.Workbench.close(Workbench.java:853)
    at
    org.eclipse.ui.internal.Workbench.close(Workbench.java:828)
    at
    org.eclipse.ui.internal.Workbench$23.handleEvent(Workbench.java:1848)
    at
    org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
    at
    org.eclipse.swt.widgets.Display.sendEvent(Display.java:3484)
    at
    org.eclipse.swt.widgets.Display.messageProc(Display.java:2675)
    at org.eclipse.swt.internal.win32.OS.DefWindowProcW(Native
    Method)
    at
    org.eclipse.swt.internal.win32.OS.DefWindowProc(OS.java:1927)
    at
    org.eclipse.swt.widgets.Shell.callWindowProc(Shell.java:443)
    at
    org.eclipse.swt.widgets.Control.windowProc(Control.java:3334)
    at
    org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1539)
    at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:1634)
    at
    org.eclipse.swt.widgets.Display.windowProc(Display.java:4025)
    at org.eclipse.swt.internal.win32.OS.PeekMessageW(Native
    Method)
    at
    org.eclipse.swt.internal.win32.OS.PeekMessage(OS.java:2401)
    at
    org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2963)
    at
    org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1930)
    at
    org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1894)
    at
    org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:422)
    at
    org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
    at
    com.adobe.flexbuilder.standalone.FlexBuilderApplication.run(FlexBuilderApplication.java:1 03)
    at
    org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
    at
    org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLau ncher.java:92)
    at
    org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.jav a:68)
    at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
    at
    org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown
    Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown
    Source)
    at java.lang.reflect.Method.invoke(Unknown Source)
    at
    org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
    at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
    at org.eclipse.core.launcher.Main.run(Main.java:977)
    at org.eclipse.core.launcher.Main.main(Main.java:952)
    !ENTRY org.eclipse.ui 4 4 2007-06-13 16:34:19.959
    !MESSAGE Unhandled event loop exception
    !ENTRY org.eclipse.ui 4 0 2007-06-13 16:34:19.959
    !MESSAGE PermGen space
    !STACK 0
    java.lang.OutOfMemoryError: PermGen space

    Hi Rogier,
    Can you please log it in our new public bug system:
    http://bugs.adobe.com/flex?
    It'd be great if you can provide more info to the bug e.g.
    details of your simple AIR project, platform, FB version (Plugin or
    Standalone).
    thanks,
    Sharon

  • [N95 8GB]Out of Memory error when opening 15MB pdf...

    What is the file size limit when opening a pdf file? I have a 15MB pdf file that cause 'Out of memory' error when I opened it with the PDF Reader that comes with the phone.
    Thanks.

    Hi,
    It seems that problem is file specific, so could you please share a file with me. I sending you a private message.
    Regards,
    Anoop

  • Cannot see images occassionally: "Out of memory"

    Hi,
    I love Lightroom, but have the problem that is really interfering with my work. When I look at a larger collection of images (100+), every now and then the image area will be greyed out, and it will say 'Out Of Memory' in red (upside down and back to front) in the lower left corner.
    This never happens when I am looking at thumbnails in Library-mode. It does happen when I am looking one image in Library-mode, in deverloper mode, and frequently in the Slide-show mode. Interestingly enough: when an image is not visible in Library-mode, chances are it is visible in Developer-mode and Slide-show (and vice-versa).
    I use Lightroom for a lot of subtle retouching, so I can imagine the files are large. I would understand in Slide-show that the CPU simply doesn't have the time to render the image with all the alterations I apply to it -- but in Developer and Libarary-mode I can wait and wait, and the image nevr shows up. Then I go to Developer, and there it is!
    I store my images on a seperate dedicated external harddisk connected through USB 2.0. I have browsed through the forum already, and found a solution in changing the windows pageview setting. I did this, but it made no difference. The problem still occurs with the same frequency. I have not installed LR 1.1 yet; the negative reports on this forum have scared me: I really don't need my database messed up right now.
    Any suggestions you might have will be greatly appreciated!
    Rogier Bos
    Rotterdam, The Netherlands.

    Guys,
    Before I start this rant... I LOVE LIGHTROOM... but no more ADOBE, I cannot stand it anymore... sort out the OOM errors now, before I put my Lightroom CD into the shredder and then post this SHAM on every ADOBE forum I can find.
    I have experienced the out of memory error 11 times today. I am working with 30,000+ images in Lightroom 1.1 on XP, but only looking through 58 files while doing an import of 100 files I get the "OUT OF MEMORY A2" error. This looks suspiciously like another of the, now famous, debug errors used by the developers to track the 'pain' issues. I would challenge Adobe that they know EXACTLY why this happens, a limitation in the programming techniques for their chosen development platform is highlighting issues in the Windows Memory sub-system and they cannot do diddly squat about it... they are just 'attempting' to clean up memory leaks where they can, by putting markers (A2) into the code. It would seem that they are down a creek without the proverbial paddle.
    Tom Hogarty & ADOBE listen up... stabilize the memory issues stop listening to your marketing bods who are probably leaning over your shoulder as I write these words. You are going to suffer at the hands of Aperture and Capture One if you dont get your act together. I have used both of the above with little or NO errors at all.
    Tell us ADOBE why do none of your engineers or developers talk openly about OOM errors, stop silencing them... lets get a discussion going there are some very capable developers out there willing to help for FREE! Are you mad... admit the problems and get people to help... Open Standards could teach you guys a thing or two!
    Remember for everyone of of us that actually has the balls to complain, there are a 1000 who just sit and suffer not knowing what to do!
    Fix the OOM issues before you do anything else this week!! Provide an interim 1.1.x update and make people happy they bought ADOBE and above all else remember at the end of the day these people PAY your wages.
    ...Now where is my Capture One license key...
    Damon Knight
    Photographer
    London

  • Report with more than 600 kb image - BO Server getting Out Of memory Error

    Hi,
       We have a report which displays images and size is above 600 KB.We are getting an "Out Of memory" Error while previewing this report in Business Object Server.
    In another situation we tried by giving a dynamic path to the OLE object, but the report is not showing error. We are not able to view the image whose size is more than 600KB
    Notes: 1. Image is stored as a BLOB  in Oracle Database
               2. Connection used inside the report is OLEDB
               3. UNIX Environment
    Regards,
    Sathish

    Please re-post if this is still an issue to the Business Objects Forum or if you have a valid support contract create a case on line.

  • Out of Memory error caused by huge result set

    Hi,
    I'm using version 3.3.4 of KODO with the enterpise license. Our
    application has some places where we're using straight SQL to create a
    query using the following statement:
    Query query = pm.newQuery ("javax.jdo.query.SQL", queryString);
    There is one query that performs an inner join and returns over 2 billion
    results. Of course this throws an out of memory error when we try to add
    the results to a list. I printed out the exact SQL statement that is
    being executed and it should return 0 results. The application is hitting
    an Oracle 9i database, and running the query through the Oracle tool
    SQLPlus returns the correct result. I'm stumped as to why this massive
    result set is being returned when we use KODO. Here is the SQL string for
    your examination:
    SELECT T_ORDERITEM.* FROM T_ORDERITEM INNER JOIN T_REVENUE ON
    T_ORDERITEM.ORDER_HOID = T_REVENUE.HOID WHERE T_ORDERITEM.COMMODITY_HOID
    = '1871816913731466' AND T_ORDERITEM.DATESHIPPED BETWEEN
    TO_DATE('12/25/2005', 'MM/DD/YYYY') AND TO_DATE('01/24/2006',
    'MM/DD/YYYY') AND T_REVENUE.CUSTOMER_HOID IN (1844203535241210)
    Thanks for your help,
    Bennett

    I'm also using JDK 1.4.2 so I'm not sure why you wouldn't be running into
    the issue using the ArrayList constructor.
    -Bennett
    Paul Mogren wrote:
    What result list implementation are you using? What's your JDK
    version? I'm sure I've written new ArrayList(results) numerous times
    without trouble, though I have not used Kodo 3.3.4. I had a look at
    the JDK 1.4.2 source code for ArrayList(Collection) and
    ArrayList.addAll(Collection), and it looks to me like the latter would
    consume more memory than the former. However, it might be worth noting
    that the former invokes size() on the argument.
    -Paul Mogren, CommerceHub
    On Thu, 19 Jan 2006 22:10:50 +0000 (UTC), [email protected]
    (Bennett Hunter) wrote:
    Nevermind, issue resolved. This wasn't due to the query, but rather how
    we were creating a list with the results returned. This issue is probably
    already posted, but I'll give the info. again:
    You can't create an arraylist by passing in the kodo collection of results
    to the constructor of ArrayList. For example: List l = new
    ArrayList(results) .... that will throw the out of memory error because of
    the way that the constructor builds the kodo collection. Maybe the bug is
    with the kodo collection. However, the way around this is to create the
    list with an empty constructor and then do an addAll() operation.
    Bennett Hunter wrote:
    Hi,
    I'm using version 3.3.4 of KODO with the enterpise license. Our
    application has some places where we're using straight SQL to create a
    query using the following statement:
    Query query = pm.newQuery ("javax.jdo.query.SQL", queryString);
    There is one query that performs an inner join and returns over 2 billion
    results. Of course this throws an out of memory error when we try to add
    the results to a list. I printed out the exact SQL statement that is
    being executed and it should return 0 results. The application is hitting
    an Oracle 9i database, and running the query through the Oracle tool
    SQLPlus returns the correct result. I'm stumped as to why this massive
    result set is being returned when we use KODO. Here is the SQL string for
    your examination:
    SELECT T_ORDERITEM.* FROM T_ORDERITEM INNER JOIN T_REVENUE ON
    T_ORDERITEM.ORDER_HOID = T_REVENUE.HOID WHERE T_ORDERITEM.COMMODITY_HOID
    = '1871816913731466' AND T_ORDERITEM.DATESHIPPED BETWEEN
    TO_DATE('12/25/2005', 'MM/DD/YYYY') AND TO_DATE('01/24/2006',
    'MM/DD/YYYY') AND T_REVENUE.CUSTOMER_HOID IN (1844203535241210)
    Thanks for your help,
    Bennett

  • Out of Memory error end erratic behavior

    Brief description of the issue: while importing images at their current location, some of them would show in grid view with an exclamation mark, and LR would not allow me to adjust them. Removing and importing the same set of images again, the subset of troubled images changed. At some stage, trying to develop one of the images, I got an "Out of Memory" written in red in the center pane. PS CS opens the same images without any problem, and Windows Task Manager indicates there is plenty of available physical and virtual memory.
    Here what I did in detail.
    While I was importing images at their current location into the library from DVDs, I started to see en exclamation mark in the upper right corner of several images in the grid view. When I selected any of those images and hit "D" to develop them, I got "An unknown error occurred" in the Develop module, and LR would not allow me to do any adjustment.
    I have tried removing the images from the Library and importing them again, and then some of the troubled images were not the same as before, and LR would allow me to develop some of the previously troubled images.
    PS CS File Browser shows them all correctly, and also PS can open any of the images without any issue.
    I have copied some of the troubled images to my hard disk, and then tried to import them into LR from there. The same image sometimes worked, sometimes didn't. Finally, when trying to develop one of those, I got an "Out of Memory" error message printed in red and upside down in the middle of the picture.
    Windows Task Manager was reporting 833824 KB of Available Physical Memory out of 2095536 KB, and was reporting as Commit Charge: Total 1281084 KB, Limit 5080272 KB, Peak 1707720 KB.
    Any idea what is going on? It looks to me like instability after I imported a few hundred pictures in a row.

    You are ABSOLUTELY right that I had explorer windows open when I got the export failed messages!!!! I do all my printing at costco, so I have Lr export my final pics to a 'jpeg finals' directory, and then individual sub-directories for each folder they came from, and then manually copy from each of these sub directories to the root directory on my CF card for transport to Costco.
    Will see if it happens in the future without that window open. Still wouldnt help the upside down OOM messages, tho thanks for the update that the team is working on it.
    These two issues and the UI lag are really all that I can ***** about too much, which is pretty amazing given my beta frustrations. I still wish I wasnt locked to the DB. I still cannot in good conscience recommend Lr to most new DSLR users. But for my own use I'm pretty happy. I wish I could get better highlight and shadow recovery like I got in RSP but I'm sure that is user error and n00bishness more than a failure of the app. I'm also not happy that I can't toggle the crop tool to the way I want to work permanently but I guess that ship has sailed too.

  • Out of memory error in IBM JVM

    Hi i am using websphere application server's dyna cache for getting performance optimiztion in my application.
    I am able to load values into the cache using the command cache api in the dyna cache.When i clear the cache for loading another set of values the cache gets cleared but still ,while loading the second set of values i get an out of memory error
    The dynacache is an distributed map
    i want to know whether the error is due to improper garbage collection
    on this map,if so help me to overcome this
    The JVM configuration are as follows
    Min 256mb
    Max 768mb
    I have a total of 1Gb ram

    Maybe your program's memory usage is rubbing against the upper limit, and something about the latest JVM caused it to break through.
    Try using the command line parameter -mx500m (for 500 megs or whatever amount you neeed)

  • Out of memory Error in ADF appication

    Hi All,
    I am using JDev 11.1.2.1.0.
    In my application we are performing the following activities.
         1. File Upload
         2. File download
         3. inputListOfValues(Magnifier LOV where we will be loading thousand of row in search results table).
    And our application should support 50 concurrent sessions at any point of time.
    Right now Our JDev is configured with a Heap Space of 512MB.
    We are getting out of memory error in the Jdeveloper console if we test the application with <20 concurrent sessions and it is not if test with less concurrent sessions(Note our Application Module settings configured to support 50 Concurrent sessions).
    Is there any way that we can avoid Out of memory error. Please suggest any tools through which we can track the objects causing the Memory leak.
    please suggest.
    thanks in Advance.
    Veer

    inputListOfValues(Magnifier LOV where we will be loading thousand of row in search results table).
    If you load and scroll over thousands of VO rows, then the VO will load all these rows in memory if the VO has not been configured to do Range Paging, which may cause out of memory. By default, VOs are not configured to do Range Paging. Please, try with VO Range Paging in order to minimize VO's memory footprint. (When a VO is configured to do Range Paging, it will keep in memory only a couple of ranges of rows. The default range size is 25, so it will keep in memory a few tens of rows). UI does not need to be changed and the user will scroll over the rows in an <af:table> in the normal way as he/she used to.
    Right now Our JDev is configured with a Heap Space of 512MB.
    JDev's heap size does not matter. The heap that you should check (and maybe increase) is the Java heap of the Integrated Weblogic Server, where the application is deployed and run. The heap size of the Integrated WLS is configured in the file <JDev_Home>/jdeveloper/system.xx.xx.xx.xx/DefaultDomain/bin/setDomainEnv.cmd (or .sh).
    Please suggest any tools through which we can track the objects causing the Memory leak.
    You can try Java Mission Control + Flight Recorder (former Oracle JRockit Mission Control), which is an awesome tool.
    Dimitar

  • Jrockit out of memory error

    We are getting out of memory error with jrockit1.4.2_08. We used memory debugger tools to find the leak. Apparently there do not seem to be a leak from application perspective. Here is the core dump. Please help me resolve this.
    ===== BEGIN DUMP =============================================================
    JRockit dump produced after 0 days, 05:37:55 on Thu Jun 5 20:39:11 2008
    Additional information is available in:
    /opt/obs/obs_app/obs31.0/user_projects/admin/jrockit.17430.dump
    No core file will be created because core dumps have been
    disabled. To enable core dumping, try "ulimit -c unlimited"
    before starting JRockit again.
    If you see this dump, please open a support case with BEA and
    supply as much information as you can on your system setup and
    the program you were running. You can also search for solutions
    to your problem at http://forums.bea.com in
    the forum jrockit.developer.interest.general.
    Error code: 52
    Error Message: Null pointer exception in native code
    Signal info : si_signo=11, si_code=2
    Version : BEA WebLogic JRockit(TM) 1.4.2_08 JVM R24.5.0-61 ari-49095-20050826-1856-linux-ia32
    Threads / GC : Native Threads, GC strategy: parallel
    : mmHeap->data = 0x40416000, mmHeap->top = 0x7ec16000
    : mmStartCompaction = 0x45236000, mmEndCompaction = 0x4a056000
    CPU : Intel Pentium 4 (HT)
    Number CPUs : 4
    Tot Phys Mem : 4021997568
    OS version : Red Hat Enterprise Linux ES release 2.1 (Panama)
    Linux version 2.4.9-e.72smp ([email protected]) (gcc version 2.96 20000731 (Red Hat Linux 7.2 2.96-129.7.2)) #1 SMP Tue Jul 3 22:04:51 EDT 2007
    State : JVM is running
    Command Line : -Djava.class.path=<my own jars list>
    java.library.path=/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/jrockit:/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386:/opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/../lib/i386:/opt/mqm/java/lib:/opt/tib/rv7.1.2/lib:/opt/obs/obs_app/obs31.0/thirdparty:/opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686:/opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/oci920_8
    C Heap : Good; no memory allocations have failed
    Registers (from context struct at 0x8d5b724/0x8d5b80c):
    EAX = 000005f4 EBX = 0000007f
    ECX = 7ff8bd90 EDX = 24a18f94
    ESI = 7ff46af0 EDI = 00000100
    ESP = 7f262bc0 EIP = 4026d58f
    EBP = 7f262bd8 EFL = 00010203
    CS = 0023 DS = 002b ES = 002b
    SS = 002b FS = 00df GS = 00df
    Stack:
    7f262bc0 :00000000 7ff46af0 00000f94 00000000 00028000 00000000
    7f262bd8 :7f262c08 401ffcae 7ff8bd90 24a18f94 00028000 a0000000
    7f262bf0 :0a5f1800 7f262c74 08d137a0 00000050 00000000 7f262c34
    7f262c08 :7f262c48 4028a7fb 24a18f94 00000000 08d137a0 08d139e4
    7f262c20 :581a664c 00000003 08d137a0 00000001 7f262c74 00000000
    7f262c38 :7f262ca8 402c28bd 7f262c74 20040144 7f262ca8 402c292f
    7f262c50 :7f262c74 00000000 00000000 7f262c84 581a6640 08d137a0
    7f262c68 :08d1382c 414d2db8 210d41e8 0a5f1800 08d137a0 7f262d9c
    7f262c80 :24a18f95 00000002 00000000 7f262cf8 08d1382c 581a6640
    7f262c98 :00000000 00000000 00000000 00000000 7f262ce8 402e0861
    7f262cb0 :08d137a0 581a6640 00000020 7f262cf8 210cc499 00000001
    7f262cc8 :00000000 7f262ce4 08d139e8 7f262cf0 581a66c0 53b8d780
    7f262ce0 :00000000 00000020 08d137a0 210cc43e 08d1382c 08d139e4
    7f262cf8 :08116840 08d139e4 00000000 581a6400 210b41ff 00000001
    7f262d10 :581a6618 581a6560 210cc499 581a6565 581a6618 581a6560
    7f262d28 :210d2744 581a62f0 581a6560 210d2725 2112a995 2112a985
    7f262d40 :2112a975 23a67584 581a6578 00000001 00000001 220e35a9
    7f262d58 :23a53381 581a62f0 00000000 00000000 581a6548 00000046
    7f262d70 :00000000 00000002 00000000 581a62f0 00000001 00000000
    7f262d88 :00000000 00000000 581a6530 581a62f0 23a56e15 24a18f95
    7f262da0 :24a18ba3 00000000 581a6130 210bead9 581a6038 581a6038
    7f262db8 :581a6038 53b88f50 40fa9ca8 581a6308 55b54b00 40fa9c38
    7f262dd0 :80000000 55a06030 581a6020 581a6038 581a6020 24a189bb
    7f262de8 :40fa9c38 581a6020 40fa9ca8 581a60c0 55a06030 53942ff8
    7f262e00 :55b54b00 40fa9ca8 40fa9c38 08d137a0 7f262e24 210b34d8
    7f262e18 :40fa9c38 40fa9c68 40fa9ca8 24a18800 402e3a4d 7f262fb3
    7f262e30 :0000002c 00000003 7f262ec4 08d1382c 24b196e0 249c4f84
    7f262e48 :581a5390 00000000 00000058 7f262e84 402b861a 249c4f84
    7f262e60 :7f262e80 08d1382c 00000001 00000001 00000008 00000013
    7f262e78 :00000005 581a5fd8 08d139dc 7f262e18 00000003 00000005
    7f262e90 :00000005 00000000 00000000 55a06030 55b54b00 7f262e24
    7f262ea8 :7f262e24 08d137a0 7f262ee0 24a18800 210b34a0 0000002c
    7f262ec0 :7f262fb3 7f262f04 402c8931 08d1382c 1aea85c0 24b196e0
    7f262ed8 :00000000 7f262f5c 402c8b74 7f262f54 401aaab0 00000000
    7f262ef0 :7f262f5c 7f262f54 401aaab0 401aa6a0 1aea85c0 7f262f64
    7f262f08 :402c8c41 08d1382c 249c4f84 00000000 7f262f5c 402c8b74
    7f262f20 :00000000 7f262f54 08d13dd0 08d1382c 7f262f9c 00000000
    7f262f38 :00000000 7f262f7c 402f2b2d 08d137a0 00000001 7f262f7c
    7f262f50 :402f2b24 08d13dd0 402f2b24 7f262fd4 08d1382c 7f262f94
    7f262f68 :402dbd4c 08d1382c 08d139dc 249c4f84 7f262fd4 08d139e4
    7f262f80 :581a5ee0 00000000 476bd4c0 210b67f6 00000000 08d137a0
    7f262f98 :210e7b1b 08d1382c 08d139e0 249c4f84 08d139dc 7f262fd4
    7f262fb0 :083e6898 08d139dc 00000000 210eb30d 40fa9ca8 210eb184
    7f262fc8 :405bff10 00000005 210e7c48 581a5fb8 581a5fb8 581a5fe0
    7f262fe0 :00000000 00000000 581a5690 210e7253 581a5fb8 00000009
    7f262ff8 :73a44aa8 73a44aa8 00000005 581a5fb8 00000009 581a5690
    7f263010 :246e7cd0 581a5fb8 581a53e8 581a5f48 40fa9b90 40fa9be8
    7f263028 :55a06030 55b54b00 40fa9be8 40fa9bd0 246e7b13 55b54b00
    7f263040 :55a06030 40fa9b60 55b54b00 55a06030 581a5378 246e79b6
    7f263058 :55a06030 55b54b00 57712968 405c6858 40fa9b40 00000001
    7f263070 :40fa9b40 2426bab4 55a06030 57712968 57712928 57712968
    7f263088 :55b54b00 55b54b00 4b345448 2426ba1b 2426b717 53b88f50
    7f2630a0 :405c6858 5393c038 53b88f50 00000002 53b88f40 24266f1f
    7f2630b8 :53b88f50 53b88f50 53b88f40 5393c038 53b849c0 00000000
    7f2630d0 :53912b90 5393acd0 5393c038 53912b90 242613c8 5393c038
    7f2630e8 :00000000 5393acd0 00000000 5393aa60 5393c038 24658a31
    7f263100 :5393acd0 4a0dbf40 00000000 4a0dbf40 539125c0 23a74a88
    7f263118 :539126e8 00000001 6553be00 539125c0 246587dc 53ebb610
    7f263130 :4a0dbf40 00000000 4a124210 00000000 00000000 5393aa60
    7f263148 :218aff64 09ccec00 221aa582 5393a440 4a1507e8 4a1507e8
    7f263160 :536f07d8 533cdee0 5393a440 533cdee0 000378b6 536f07d8
    7f263178 :5393a430 00000004 210b48f0 00000050 0000000f 211080dd
    7f263190 :40576ec8 21108145 5393a480 5393aa60 5393aa60 21108074
    7f2631a8 :00000003 536f07d8 4a124210 7d1c9048 5393a430 654d5040
    7f2631c0 :4a090428 232a5328 7d1c9048 4a124210 229f2aeb 7d1c9048
    7f2631d8 :4a124210 4a127090 538f80a8 654d5040 536f07d8 4a127090
    7f2631f0 :536f07d8 242438f0 536f07d8 7d1c9048 7d1c9048 538f80a8
    7f263208 :5393a418 7d1c9048 229f2a12 536f07d8 7d1c9048 22147208
    7f263220 :40528fa8 4056b138 00000000 00000000 405d4858 7d1c9048
    7f263238 :2214718a 5393a418 7d1c9048 229f239d 5393a418 536f07d8
    7f263250 :7d1c9048 4056b138 41356f20 00000000 536f07d8 40528fa8
    7f263268 :4a127090 7d1c9048 5393a418 538f80a8 42562b68 538f81e0
    7f263280 :229f2230 219161d1 41356f20 218e2089 42562b6d 41356f20
    7f263298 :7f2632b4 210b8c73 402e37ef 7f2633e8 08d137a0 7f2632b4
    7f2632b0 :210b3478 210b8c60 402e3a4d ffffffff 00000010 00000000
    7f2632c8 :7f263354 08d1382c 200920e0 200282cc 00000000 00000000
    7f2632e0 :00000000 7f263314 402b861a 200282cc 7f263310 08d1382c
    7f2632f8 :00000001 00000001 00000006 00000006 00000001 08d137a0
    7f263310 :00000000 7f2632b4 00000000 00000001 00000001 00000000
    7f263328 :00000000 00000000 42562b68 7f2632b4 7f2632b4 08d137a0
    7f263340 :00000000 210b8c60 210b3440 00000010 ffffffff 7f263394
    7f263358 :402c8931 08d1382c 080d97e0 200920e0 00000000 7f2633e8
    7f263370 :402e3550 7f2633cc 00000000 08d1382c 08d1382c 7f263aac
    7f263388 :00000000 00000000 080d97e0 7f2633d4 402c9e9f 08d1382c
    7f2633a0 :200282cc 00000000 7f2633e8 402e3550 00000001 7f2633cc
    7f2633b8 :00000000 00000000 00000000 00000000 00000000 00000000
    Code:
    4026d48f :83403d9a 008bf4c4 166be850 c4830009 f4c48310 a817e853
    4026d4a7 :b70f0009 c0010643 06438966 0ff8c483 048dc0b7 02e0c140
    4026d4bf :08438b50 57b7e850 43890003 20c48308 53f4c483 09a87ce8
    4026d4d7 :9a38a100 8b64403d 30050300 83403d9a c48310c4 50008bf4
    4026d4ef :0915f4e8 084b8b00 4574c985 0f0c558b 8d0443b7 14894004
    4026d507 :10558b81 0443b70f c140048d 430302e0 04508908 0f14558b
    4026d51f :8d0443b7 e0c14004 08430302 66085089 b80443ff 00000001
    4026d537 :b48d09eb 00000026 8bc03100 ec89e85d 768dc35d e5895500
    4026d54f :570cec83 458b5356 08558b08 00fc45c7 83000000 b70ff4c4
    4026d567 :478d0478 8df8d101 e852ff58 0009a7ed 8310c483 4974fffb
    4026d57f :084d8b90 8b5b148d 048d0841 0c558b90 77045039 0850391c
    4026d597 :188b0f72 51f4c483 09a7fce8 ebd88900 fc5d892e 768d05eb
    4026d5af :8bdf8900 de89fc4d 8939148d 1fe8c1d0 d1101c8d 75f339fb
    4026d5c7 :08458bb8 50f4c483 09a7cce8 8dc03100 5e5be865 5dec895f
    4026d5df :e58955c3 571cec83 458b5356 fc45c70c 00000000 04788366
    4026d5f7 :c7627400 0000f845 558b0000 f8458b0c 8b084203 8b118b08
    4026d60f :388b0442 8b08428b 8b028b30 f8c48300 8b04598b 08418b10
    4026d627 :5040d829 145d2b52 52575653 10458b53 2c406850 558b4036
    4026d63f :bae85208 8bc7ddb3 c4830c55 f8458330 fc45ff0c 0442b70f
    4026d657 :7cfc4539 d8658da5 895f5e5b 89c35dec e58955f6 572cec83
    4026d66f :38a15356 64403d9a 0503008b 403d9a30 8bf4c483 5ee85000
    4026d687 :83000914 c48310c4 e45d8df4 19bbe853 b2e80009 e8000918
    Loaded modules:
    (* denotes the module causing the exception)
    0x08048000-0x0804ce46 /opt/obs/wls/jrockit-j2sdk1.4.2_08/bin/java
    0x4001d000-0x40029fab /lib/i686/libpthread.so.0
    0x4004e000-0x4006fb42 /lib/i686/libm.so.6
    0x40071000-0x4007300c /lib/libdl.so.2
    0x40075000-0x401a76e5 /lib/i686/libc.so.6
    0x401b2000-0x40388eef* /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/jrockit/libjvm.so
    0x7ec57000-0x7ec66fa5 /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libverify.so
    0x7ec75000-0x7ec94a0f /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libjava.so
    0x7ec9c000-0x7ecae3ba /lib/libnsl.so.1
    0x7ec97000-0x7ec98705 /opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/libweblogicunix1.so
    0x7f5f2000-0x7f5f3eff /opt/obs/wls/wls8.1sp3/weblogic81/server/lib/linux/i686/libmuxer.so
    0x7f5f6000-0x7f5f95c1 /opt/obs/wls/jrockit-j2sdk1.4.2_08/jre/lib/i386/libioser12.so
    0x80318000-0x8031f8bf /opt/obs/obs_app/obs31.0/thirdparty/libXMLC.so
    0x80344000-0x8034c66f /opt/tib/rv7.1.2/lib/libtibrvj.so
    0x8034e000-0x803563e0 /opt/tib/rv7.1.2/lib/libtibrvcmq.so
    0x803d2000-0x803e66bb /opt/tib/rv7.1.2/lib/libtibrvcm.so
    0x7fef9000-0x7fefdcaf /opt/tib/rv7.1.2/lib/libtibrvft.so
    0x803e8000-0x804341a4 /opt/tib/rv7.1.2/lib/libtibrv.so
    Thread Stack Trace:
    WARNING: Memory exhausted
    at java/lang/Throwable.fillInStackTrace0(Native Method)@0x210cc3f0
    at java/lang/Throwable.fillInStackTrace(Unknown Source)@0x210cc499
    at java/lang/Throwable.<init>(Unknown Source)@0x210d2744
    at java/lang/Exception.<init>(Exception.java:41)@0x210d2725
    at java/lang/RuntimeException.<init>(RuntimeException.java:43)@0x2112a995
    at java/lang/IllegalArgumentException.<init>(IllegalArgumentException.java:36)@0x2112a985
    at java/lang/NumberFormatException.<init>(NumberFormatException.java:38)@0x2112a975
    at java/lang/NumberFormatException.forInputString(NumberFormatException.java:48)@0x23a67584
    at java/lang/FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1207)@0x220e35a9
    at java/lang/Double.parseDouble(Double.java:220)@0x23a56e15

    I can't tell from the crash dump what the exact problem is - maybe you are running out of native memory?
    You are running a very old JRockit version. Since you are a Oracle/BEA customer, you can get a newer one from BEA Support, or through edelivery.oracle.com.
    -- Henrik

  • Out of Memory error, though nothing has changed?

    I have two large projects, 65mb each, which I have had open in FCP 7 with no problems for months.
    Then I left them closed for a month and worked on other projects.
    Now I can't open either of those two earlier projects without receiving the Out of Memory error (I'm trying to open each one individually). There are many things to look for when this error appears, as found all over this forum and others. So here is my checklist of facts:
    Neither project contains any PSD files or any sequences with text files in them.
    One of those projects contains no sequences whatsoever, only clips.
    All media for these projects is Apple AVC-Intra 100M 1280x720.
    The RAID drive containing the media for these projects has not been used since the last time the projects were open and working fine.
    The edit system has not changed in any way:
    - FCP 7.0.3
    - Mac Pro
    - OS 10.6.6
    - 2x2.66 Quad Core
    - 6 GB RAM
    - LaCie 8TB RAID, with 1.7TB free
    All RAM is functioning fine.
    I've trashed FCP preferences and received the same results anyway.
    Again, both projects were working fine on this same computer, same version of FCP, even with BOTH projects open at once.
    Also, I've been working with other projects on this same system with no problems, some nearly as large as these two.
    So... none of the obvious culprits are at work here to cause this error, unless I'm missing something.
    Anyone have any ideas? This is a bit scary, as these are documentary projects which are only going to get bigger, and I've done projects bigger than this several times without problems. Hopefully I'm missing something simple...
    Thanks.

    I think I found the culprit, and it's an obvious one:
    My original big project, 65mb, had a bin that was created by an assistant before I began work on the project and I never saw it. That bin has sequence strings for every tape/card loaded into the project, so it had about 65 rather long sequences. Once I found it, I moved that bin to its own project and deleted it from the original project.
    Now the original project opens, and I can open multiple projects at once, no Out of Memory error.
    So it's the bin full of sequences that did it. If I had seen that bin before I wouldn't have had to run this up the flagpole here. But at least it reinforces that word of advice that has appeared in many previous posts about this error: Don't overload a project with long sequences. Break up the sequences into smaller projects and archive them.
    And my own addition to that advice: If you're an assistant setting up a project for an editor, make sure your editor knows what sequences you've tucked away in bins hidden inside bins inside bins, etc.
    All good to go! (Until the next error... stand by...)

Maybe you are looking for

  • Cannot awake from sleep after CPU replacement.

    I recently upgraded my arch machine from E4500 CPU to a E6700 CPU. Everything seems to be okay, but for some reason I can no longer awake from suspension. My computer kind of just sits with the little blinking white under score at the top of the scre

  • Newsstand for Yosemite?

    When will Apple do the right thing and release Newsstand for Yosemite? I thought the big hype around this new operating system waas to make information available across all ios platforms? I dont have a ipad anymore, and reading my mag subscriptions i

  • Regex for Java comments

    Hi everyone, Can anyone be so kind and post the simplest working regex pattern that matches all Java comments (multi-line, not in quoted strings, etc). I'm starting to use (Java) REs and have been fighting with various combinations of |s, $s, \\*s, P

  • Gentoo Linux RotateEffect.java wont work?

    I'm trying to run the TestEffect and RotateEffect code from the JMF solutions but it will not run under Gentoo Linux with this error: java TestEffect file:bluescreen2.mov Video format: JPEG, 160x120, FrameRate=12.0, Length=3574 The input format is no

  • Planning run multiple creation of PR

    Dear Friends Please guide me how to control the automatic creation of multiple purchase requisitions when doing a planning run for a project, coz when i do a planning run for a project, many purchase requisition are being created buit we need only on