"Out of Memory" error every 10 minutes, never happened before.

Hello, let me go right to my problem.
I'm using Photoshop CS5, AMD Athlon II X4 635 Processor - 2,90 GHz, got 4gb RAM and 32bit Windows 7. Also an ATI Radeon HD 5700
I'm studying communications designs so I'm using Photoshop a lot. I've been using CS5 for quite a while now (like 3 months) and it never made any problems, except crashing every now and again which I didn't mind that much.
Since today though, it always gives ma a "Out of RAM Memory" Error, when I try to save, use the brush tool, or pretty much anything else, after like 10 minutes of working on a picture. The pictures I work on aren't big, the psd file is something like 30mb and I handled pictures that were 10 times bigger in the past, without getting that error. I don't use "content aware fill" which I often heard was the cause for this and I don't have anything except Photoshop opened when I'm working on a picture. I already increased the pagefile in windows, I raised the cashe settings in Photoshop to the maximum and still, the error occurs like 10-15 minutes after I start up Photoshop and start working on my picture.
Also, before all of that started to happen today, photoshop crashed an awful lot and I started to save more frequently, like once every 5 minutes.
Please, can anyone try to help me find a solution to this?

I am sorry,
I didn't realize my post said, "Hey idiot, check your hard drive to make sure you have the room for your page file to grow."
I would like to point out this is a user forum you came to asking other users for help with an issue you are experiancing and those of us who post try to help point you in the right direction. There really is no need to be rude or get offended from a suggestion.
Good luck with your issue.

Similar Messages

  • Out Of Memory Error every time my playhead reaches a slug I placed in timel

    The past two days in one particular project I get an Error: Out Of Memory every time I play from the timeline and the playhead reaches the slugs I placed for the commercial breaks. I thought maybe the problem was with the commercial sequence I placed over the slug but I deleted it and still get the problem. When I get the message and then advance the playhead a little further to the right, but still over the slug, and press play I get a loud static cracking sound and the error message reappears. When I advance the playhead and hit play again FCP crashes. This happens in this order every time I reach a slug in the timeline. I am using FCP 6.0.5 (reinstalled last night) the project is HDV 1080i60 and I have a Mac Pro Quad Core with 6 GB of memory and I am saving to a esata Raid drive. I have ordered new memory although I do not think that is the problem. Why does stuff like this happen every time a deadline approaches?

    meh... spoke too soon! I find that edit-to-tape (assembly edit on Sony HVRM-15 DVCAM mode) is unreliable whenever there is a slug in the timeline. Typically playhback crashes a few seconds after we hit the slug.
    Im working around this by either using "black" clips rather than slug, or by dumping out the entire sequence to a separate QT movie, and then sending that out to tape.
    Its puzzling that my current-gen quad-core mac pro (4GB memory total, NVIDEA 8800 card, seagate 250GB internal video drives) seems to be having such a hard time handling this...

  • I'm seeing adobe crash messages every 5 minutes.Never happens on IE11.I've followed suggestions,none work.I'm ready to leave for good.

    you've seen this complaint from many over the last few months. I've accepted all Mozilla updates and still the problem persists on two different computers that I use.
    There are websites that I can't even access using Firefox. Isn't there some official protocol that you must adhere to?
    I'm quite tired of the frustrations using what used to be the Finest web browser available.

    hello, could you provide your latest few submitted crash reports? please enter '''about:crashes''' into the location bar, copy the latest few report ids from there starting with '''bp-''' & paste them here into a forum reply. this will give us a better understanding what may be triggering those crashes.

  • Out of memory error, possibly corrupted fs?

    I just got my tour, and I love it. However I ran into a weird problem.
    The desktop manager never show the BB messager as installed, then it tries to uninstall it. If I check the checkbox it installs over it and breaks it.
    I was able to fix the messanger by reinstalling over the old one from the app store OTA.
    Now, vilingo wont run, it throws an out of memory error. I've tried removing it and reinstalling it every way I can think of.
    Also sometimes it takes 20+ minutes to reboot.
    The crux of the matter is I could easily exchange it at this point, do you think I should or should I wipe it? any other suggestions?
    Thanks,
    Chance

    No, not corrupted. You are out of memory..... just like a computer that is bogged down with too much stuff, your phone can only handle so much. The reason your apps keep disabling is most likely it is archiving them to make room for everything else you've got going. The biggest memory muncher is most likely pics or videos... as few as 5 or 6 pics and throw your phone off.  The other thing you might be noticing is missing call logs, messages, or emails.... again, the phone is automatically clearing them out of memory (possibly before you[ve even had a chance to view them) to make room for everything else you've saved to it.
    As far as startup times, again... MEMORY. the more files the blackberry has to scan through when it starts up (and it scans EVERY file EVERY time) the longer its going to take.
    The solution for all of these issues is to get a memory card and use your desktop software to transfer all of the pic video and ringtone content to it. you can transfer one the phone itesself but its a time consuming process.  after this is done pull your battery... startup still takes about 10 min on the tour but you should be ok.  The phone will automatically save media to the SD card once its installed. 

  • Question - Out of memory error

    Receiving "Out of Memory" error when trying to insert pages into an existing pdf.  I'm using Acrobat 9 Standard version 9.5.1.

    I downloaded JProfiler.
    Even though I'm new to Java and only had JProfiler for an hour or two
    I was able to get my app running from JProfiler and observe the heap
    in real time. I saw that when I first run the server app it is level then when
    I pull up the client lobby and then the chat room up it begins to climb very
    quickly going from 1 to 10 MB in a matter of a couple minutes and continues
    to rise fast. I checked the code closer and realized that I could close the
    prepared statment and resultset each time I go through the loop. Here is the
    code I added inside the loop at the end of the loop mentioned above.
    rs.close();
    ps.close();
    out.flush();
    System.gc();
    I ran the JProfiler again and the heap saw toothes right at 1 MB and stays there :) .
    I let it run for 10 minutes. It looks like it is still climbing a couple bytes every
    minute but like I said there are other threads in the app running so as I learn
    how to use JProfiler more and more I should be able to run that down as well.
    Made me feel alot better about the whole situation.
    One last ? When I use the line
    while (keepgoing) {
    switch (new Integer(in.readLine())) {
    within the keepgoing loop does the new Integer(
    use more and more memory each time it loops or is that collected since it is not referenced again?
    So looks like I will have to buy JProfiler even though i'm dirt poor lol. Thanks.

  • "Out of memory" error when compiling loki-like templates w/Typelists

    Using Forte C++ 5.3 with the latest [2002/03/20] patches, attempts to compile a loki-like Functor template [download at www.awl.com/cseng/titles/0-201-70431-5 or see "Modern C++ Design" by A. Alexandrescu] whose family of operator()() functions take up to 15 parameters cause an "Out of memory" error. The top(1) command showed that the complier's process size exceeded 2.0G and that the compiler had run for 20+ minutes.
    At 10 parameters, the compiler quickly [ <2 minutes ] and successfully compiles the same source. At 11 parameters, the compilation is very slow [ >5 minutes] yet still successful.
    Platform: SPARC SunFire 280R 500MHz

    I'm having similar problems:
    One source file that has a 13 argument recursive template takes a long time to build, and uses almost .75GB. Optimized builds of the same file never complete, and fail with:
    SunWS_cache: Error: Error occurred in invoked compiler, /opt/SUNWspro/bin/../WS6
    U2/bin/CC [process fork failure, errno = 12]. Aborting....
    operator()() functions take up to 15 parameters cause
    an "Out of memory" error. The top(1) command showed
    that the complier's process size exceeded 2.0G and
    that the compiler had run for 20+ minutes.
    At 10 parameters, the compiler quickly [ <2 minutes ]
    and successfully compiles the same source. At 11
    parameters, the compilation is very slow [ >5 minutes]
    yet still successful.
    Platform: SPARC SunFire 280R 500MHz

  • 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...)

  • Photoshop CS6 has out of memory errors under Mac OS X 10.7.4

    Has anyone who has a 2008 MacBoo Pro with the NVIDIA GeForce 8600M GT 512 MB graphics card tried running Photoshop CS6 under Mac OS X 10.7.4?
    On my MacBook Pro, PS CS6 launches; however, any action results in an out of memory error.  The CS6 versions of After Effects, Premiere Pro and Illustrator all launch and run as expected under 10.7.4.
    If I switch to my Mac OS X 10.6.8 startup volume, Photoshop CS6 runs as expected.
    I have support cases open with Adobe, NVidia and Apple.  Adobe thinks I need to update the display drivers.  NVidia says display drivers must be provided by Apple.  Apple says that the display drivers are current.  The Apple support agent said that he can escalate the case if the issue can be reproduced on more than one computer.
    I'd love to keep my MacBook Pro running another year or so without having to reboot in 10.6.8 every time I need to use Photoshop.  I'd stay with 10.6.8, but of course iCloud requires 10.7.4.
    I have not tried 10.8 yet, but it's on my troubleshooting list.
    Also, PS CS6 runs fine under Mac OS X 10.7.4 on my 2010 iMac.
    Thanks in advance for any feedback.
    - Warren

    It looks like it was indeed the display driver for the NVIDIA GeForce 8600 GT 512 MB graphics card inside my 2008 MacBook Pro.
    It seems that this driver only gets installed if you upgrade from Mac OS X 10.6.7 to 10.7.4 while the startup drive is connected to the MacBook Pro itself.  I had updated while the startup drive was connected to my 2010 iMac. Accordingly, I could have reinstalled Photoshop 100 times without it ever launching as expected.  Having used the external startup drive with three other Apple computers (all 2010 or newer machines) with Photoshop CS6 launching as expected, I had just assumed (mistakenly) that it would work as expected with my 2008 computer.
    So, this was simple enough to resolve by upgrading the OS on the external startup drive while having it connected to the MacBook Pro.   In hindsight, this makes perfect sense.
    -Warren

  • Final Cut Pro 6 - 'Out of Memory/Error Code'

    Hey All,
    I'm in the final stages of editing a documentary and I keep running into an 'Out of Memory' error code in Final Cut Pro 6.0 when trying to export a reference file. The finished film is 81 minutes long and contains 19 sequences. I have all 19 sequences nested in a main sequence of a seperate FCP project file, so I'm not wasting any memory on clips or additional backups of sequences. This Nested sequence is the only sequence that exists in this 'other' project file. All of the photos used are under 4k resolution and are RGB. Even the lower thirds are animation QT's with alphas. Any thoughs would be greatly appreciated.
    Nick
    System Specs:
    Quad-Core 2GHZ MacBook Pro
    4GB DDR3 Memory
    MAC 10.7.2 (Lion)
    FCP v6.0.6

    First troubleshooting step
    https://discussions.apple.com/docs/DOC-2491
    If that doesn't solve the problem, you may have a corrupt sequence
    Try creating a new sequence with the same settings and copy the contents from the problematic sequence
    If that doesn't work.  Mark an in and an out for the first half of the sequence and do an export.  If that works, mark an in and an out for the second half and export.  Keep narrowing down the sections til you find the problematic clip. 

  • Getting out of memory errors in Indesign 5.5. What can I do to fix it?

    Getting out of memory errors in Indesign 5.5. What can I do to fix it?

    Tell your dumb friend to pay you for a new phone as he damaged it. You cannot get help here for a phone that has been taken apart, as it is not user servicible. Your dumb friend also voided your warranty and, even if the warranty were expired Apple will never touch that phone.
    Time to get smarter friends.

  • E71 keeps giving out of memory error; I can't find...

    My Nokia E71 (it's black so it may be an E71x, I guess) keeps giving me out of memory errors. I use my phone for nothing but voice calls, text messages, and emails. I have cleared all call logs, deleted all emails except 5 (they have no attachments) and cleared deleted emails, and deleted all text messages. I went into file manager and made sure there are no images, videos, etc. on the phone. I set up options to use memory card for emails. I've turned the phone off, waited 15 or 20 seconds, and turned it back on.
    I did all this a couple weeks ago. Ever since then. every couple days I get these out of memory errors, and the phone memory shows me 119 MB used and something like 300K free. I'm at the point where every few emails that come in, I have to delete all emails, erase all text messages, etc. or the phone is just too low on memory to operate.
    What else can I try? I don't have any additional applications installed. I've even tried to delete built-in apps such as RealPlayer but it didn't seem like that was possible.
    This is getting really annoying. Please help!

    @EricHarmon
    Although all user data would be deleted, have you tried resetting device to "Out of box" state by keying in *#7370# followed by 12345 (default Nokia lock code unless altered by user)?
    Happy to have helped forum with a Support Ratio = 42.5

  • N97 out of memory errors

    The product is N97, you don’t have in you drop down list!!!
    I have had my n97 for about 10 days now and everything was going brilliant. It is a stunning piece of kit.
    However on day 11. I repowered the n97, it kept on hanging the eventually got to boot after 20 attempts, but it was useless could not look up contacts. So I had taskman installed and killed loads of processes and uninstalled all the apps. It became usable as a very basic phone, but sluggish. Could use browser, maps, photos.
    The problem is I keep on experiencing out of memory errors on the phone, when I try to do basic things. I don’t know how to resolve this. I have rebooted, reset the phone to factory settings.
    Deleted data, uninstalled more apps and still no joy!! I cannot connect to ovi/pc suite to up grade the phone or roll it back.
    Symptoms the phone is sluggish it is still virtually unusable. It just barely make phones and is slow to respond to touch-screen presses and key presses.
    The taskman app says the is 47 mb free on C: drive. So I cant see what the problem is!!!
    I have always bought nokia for 10 years, never experience this sort of thing before.  I am really disappointed with this.
    Anybody else experienced this? Any ideas?
    Many thanks
    Gd
    Solved!
    Go to Solution.

    Copyless thanks for the tip.  Kudos added :-)
    I had the same problem a friend was trying to bluetooth some videos to me and I was getting Memory problem, How embarasing after a few min of my mates being impressed with the phone, and me praising it and talking about so much space and blah blah blah.
    I could not receive videos via bluetooth because they were 5MB.  WHY on EARTH can they not default this to the E: drive.
    Whoever made that decision in NOKIA should be fired what an idiot.
    Also  when I finally got to get the pictures on the phone via a computer I could not see them via the "Photos"  I had to go via the File Manager and see one by one.  AARRRRRRRRGHHH  I am getting to the point that I am going to return this phone.
    N97 Black unlocked using the 3 Network (UK). Product Code 0586308. Firmware V20.0.019. Made In Finland.Custom version V20.019.235.10.

  • Out of memory error - from parsing a "fixed width file"

    This may be fairly simple for someone out there but I am trying to write a simple program that can go through a "fixed width" flat txt file and parse it to be comma dilmeted.
    I use a xml file with data dictionary specifications to do the work. I do this because there are over 430 fields that need to be parsed from a fixed width with close to 250,000 lines I can read the xml file fine to get the width dimensions but when I try to apply the parsing instructions, I get an out of memory error.
    I am hoping it is an error with code and not the large files. If it is the latter, does anyone out there know some techniques for getting at this data?
    Here is the code
       import java.io.*;
       import org.w3c.dom.Document;
       import org.w3c.dom.*;
       import javax.xml.parsers.DocumentBuilderFactory;
       import javax.xml.parsers.DocumentBuilder;
       import org.xml.sax.SAXException;
       import org.xml.sax.SAXParseException;
        public class FixedWidthConverter{
          String[] fieldNameArray;
          String[] fieldTypeArray;
          String[] fieldSizeArray;      
           public static void main(String args []){
             FixedWidthConverter fwc = new FixedWidthConverter();
             fwc.go();
             fwc.loadFixedWidthFile();
            //System.exit (0);
          }//end of main
           public void go(){
             try {
                DocumentBuilderFactory docBuilderFactory = DocumentBuilderFactory.newInstance();
                DocumentBuilder docBuilder = docBuilderFactory.newDocumentBuilder();
                Document doc = docBuilder.parse (new File("files/dic.xml"));
                // normalize text representation            doc.getDocumentElement ().normalize ();
                System.out.println ("Root element of the doc is " +
                     doc.getDocumentElement().getNodeName());
                NodeList listOfFields = doc.getElementsByTagName("FIELD");
                int totalFields = listOfFields.getLength();
                System.out.println("Total no of fields : " + totalFields);
                String[] fldNameArray = new String[totalFields];
                String[] fldTypeArray = new String[totalFields];
                String[] fldSizeArray = new String[totalFields];
                for(int s=0; s<listOfFields.getLength() ; s++){
                   Node firstFieldNode = listOfFields.item(s);
                   if(firstFieldNode.getNodeType() == Node.ELEMENT_NODE){
                      Element firstFieldElement = (Element)firstFieldNode;
                      NodeList firstFieldNMList = firstFieldElement.getElementsByTagName("FIELD_NM");
                      Element firstFieldNMElement = (Element)firstFieldNMList.item(0);
                      NodeList textFNList = firstFieldNMElement.getChildNodes();
                      //System.out.println("Field Name : " +
                               //((Node)textFNList.item(0)).getNodeValue().trim());
                      //loads values into an array
                      //fldNameArray[s] = ((Node)textFNList.item(0)).getNodeValue().trim();
                      NodeList typeList = firstFieldElement.getElementsByTagName("TYPE");
                      Element typeElement = (Element)typeList.item(0);
                      NodeList textTypList = typeElement.getChildNodes();
                      //System.out.println("Field Type : " +
                               //((Node)textTypList.item(0)).getNodeValue().trim());
                      //loads values into an array
                      //fldTypeArray[s] = ((Node)textTypList.item(0)).getNodeValue().trim(); 
                      NodeList sizeList = firstFieldElement.getElementsByTagName("SIZE");
                      Element sizeElement = (Element)sizeList.item(0);
                      NodeList textSizeList = sizeElement.getChildNodes();
                      //System.out.println("Field Size : " +
                               //((Node)textSizeList.item(0)).getNodeValue().trim());
                      //loads values into an array
                      fldSizeArray[s] = ((Node)textSizeList.item(0)).getNodeValue().trim();   
                   }//end of if clause
                }//end of for loop with s var
                //setFldNameArray(fldNameArray);
                //setFldTypeArray(fldTypeArray);
                setFldSizeArray(fldSizeArray);
                 catch (SAXParseException err) {
                   System.out.println ("** Parsing error" + ", line "
                      + err.getLineNumber () + ", uri " + err.getSystemId ());
                   System.out.println(" " + err.getMessage ());
                 catch (SAXException e) {
                   Exception x = e.getException ();
                   ((x == null) ? e : x).printStackTrace ();
                 catch (Throwable t) {
                   t.printStackTrace ();
          }//end go();
           public void setFldNameArray(String[] s){
             fieldNameArray = s;
          }//end setFldNameArray
           public void setFldTypeArray(String[] s){
             fieldTypeArray = s;
          }//end setFldTypeArray
           public void setFldSizeArray(String[] s){
             fieldSizeArray = s;
          }//end setFldSizeArray
           public String[] getFldNameArray(){
             return fieldNameArray;
          }//end setFldNameArray
           public String[] getFldTypeArray(){
             return fieldTypeArray;
          }//end setFldTypeArray
           public String[] getFldSizeArray(){
             return fieldSizeArray;
          }//end setFldSizeArray 
           public int getNumLines(){
             int countLines = 0;
             try {
                    //File must be in same director and be the name of the string below
                BufferedReader in = new BufferedReader(new FileReader("files/FLAT.txt"));
                String str;
                while ((str = in.readLine()) != null) {
                   countLines++;
                in.close();
                 catch (IOException e) {}    
             return countLines;
          }//end of getNumLines
           public void loadFixedWidthFile(){
             int c = getNumLines();
             int i = 0;
             String[] lineProcessed = new String[c];
             String chars;
             try {
                    //File must be in same director and be the name of the string below
                BufferedReader in = new BufferedReader(new FileReader("files/FLAT.txt"));
                String str;
                while ((str = in.readLine()) != null) {
                   //System.out.println(str.length());
                   lineProcessed[i] = parseThatLine(str);
                   i++;
                in.close();
                 catch (IOException e) {}     
                //write out the lineProcess[] array to another file
             writeThatFile(lineProcessed);
          }//end loadFixedWidthFile()
           public void writeThatFile(String[] s){
             try {
                BufferedWriter out = new BufferedWriter(new FileWriter("files/outfilename.txt"));
                for(int i = 0; i < s.length -1; i++){
                   out.write(s);
    }//end for loop
    out.close();
    catch (IOException e) {}
    }//end writeThatFile
    public String parseThatLine(String s){
    int start = 0;
    int end = 0;
    String parsedLine = "";
    int numChars = getFldSizeArray().length;
    //Print number of lines for testing
    //System.out.println(numChars);
    String[] oArray = getFldSizeArray();
    //String chars = oArray[0];
    //System.out.println(chars.length());
    //oArray
    for(int i = 0; i < numChars -1; i++ ){
    if(i == 0){
    start = 0;
    end = end + Integer.parseInt(oArray[i])-1;
    else
    start = end;
    end = end + Integer.parseInt(oArray[i]);
    parsedLine = parsedLine + s.substring(start, end) + "~";
    }//end for loop
    return parsedLine;
    }//End of parseThatLine
    I have tried to illeminate as many arrays as I can thinking that was chewing up the memory but to no avail.
    Any thoughts or ideas?
    Message was edited by:
    SaipanMan2005

    You should not keep a String array of all the lines of the file read.
    Instead for each line read, parse it, then write the parsed line in the other file:      public void loadFixedWidthFile() {
             BufferedReader in = null;
             BufferedWriter out = null;
             try {
                //File must be in same director and be the name of the string below
                in = new BufferedReader(new FileReader("files/FLAT.txt"));
                out = new BufferedWriter(new FileWriter("files/outfilename.txt"));
                String str;
                while ((str = in.readLine()) != null) {
                   //System.out.println(str.length());
                   str = parseThatLine(str);
                   //write out the parsed str to another file
                   out.write(str);
             catch (IOException e) {
                e.printStackTrace(); // At least print the exception - never swallow an exception
             finally { // Use a finally block to be sure of closing the files even when exception occurs
                try { in.close(); }
                catch (Exception e) {}
                try { out.close(); }
                catch (Exception e) {}
          }//end loadFixedWidthFile()Regards

  • 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.

  • Out of memory Error with jdk 1.6

    Hello,
    I have a swing application launched on the client with the help of Java web start. The applications works fine in jre 1.4 and jre 1.5. The heap sizes are :
    initial-heap-size="5m" max-heap-size="24m"
    But when I run this using jre 1.6.0_05-b13, I am getting Out of memory Error, java heap size. And I see the memory usage is growing rapidly which I didn't notice in other jre versions (1.4 and 1.5).
    Does anyone have any idea on this?
    Thanks in advance,
    MR.

    Thanks for your response Peter. During my continuous testing I identified that error happens on jdk 1.5 also. And I have increased the min-heap-size to 24 MB and max-heap-size to 64 MB. But in that case also I noticed the out of memory error. The interesting thing is, the min-heap-size is never increased from 24MB and lot of free memory also.
    Memory: 24,448K Free: 12,714K (52%) ... completed.
    The Outofmemoryerror triggers from the reader thread which does the job of reading the data from the InputStream. One thing is we are continuously pushing more data on the output stream from the other end. Is that any limitation on InputStream which can hold some definite amount of data.
    Please throw some light on this.

Maybe you are looking for