Out of memory error adobe elements 3.0

When I try to open adobe photo elements 3.0 I get an out of memory error. the application wont even open. I upgraded my RAM from 2GB to 3 GB but it has made no difference

stacey_r79 wrote:
Hi, just wondering if you had any success in retreiving or opening your Organizer?? Im having the same problem and i have tried everything, i even rang Adobe and they told me there were no technitions able to help because Adobe Photoshop Elements 3.0 was too old. If anyone has a solution please let me know, i have 5 years worth of photos in this software, i just want to be able to open the organizer to burn all my pics to CD then i will update my software. PLEASE HELP!!!!!!!!
First of all, your photos are not, "in this software" they are in folders on your hard drive, and PSE merely points to them. If >>you personally<< didn't delete them, or reformat your HDD, then they are still there. The default file path for your photos is this; "My Documents" > "My Photos" > "Adobe", and then a couple of different folders dependent on photo type, for example, "Scanned Photos".
If you are using the default location, you can simply copy and paste you pictures to an external HDD, or burn them to CD or DVD with Windows. I am not recommending this, since if would not allow you to carry over information created by the organizer, and the photos would have to be reimported and retagged, by your files would be backed up and safe, the most important thing.
There really isn't a need for all these histrionics, Even if you uninstall PSE, your photos will still be exactly where they were. Even if you uninstall PSE, its catalog information will still be intact, and a later version will pick it up and "convert it" to its own file system.
Support for PSE-3 has obviously ended, it's more than 5 years and 5 versions old. Just as a topic of conversation, my personal favorite version of PSE, is PSE-5. IMO, it's the fasest importing, the most reliable, yet it has a lot more bells and whistles than PSE-3. If you can find a usable copy, I'd grab it, especially for a computer running XP.
As to the out of memory issue there can be several issues that can affect this, for example; not enough RAM is allotted to PSE, this is independent of the amount of RAM actually installed in the computer. The scratch disc area is full or insufficient, the preferences file is corrupt.
Everybody is complaining about not being helped in this thread, yet no one has posted back as to whether they have tried Barbara's suggestions, or even if they understand enough about Windows file system to be able to begin to help themselves.

Similar Messages

"There was an error processing a page. Out of memory." Adobe Acrobat 9 Pro-Please Help!

"There was an error processing a page. Out of memory." Adobe Acrobat 9 Pro I had this problem with my last computer over two years ago which was obviously an older version of windows and acrobat and had found a way to solve it but like I said it was an older version and was 2 years ago so I don’t remember how to fix it. I’ve looked through many forums and emptied my temp folder I’ve uninstalled and reinstalled the software I’ve turned off my anti-virus I don't have adobe reader because I know this causes comflicts also and have tried so much more and I’m still having issues with about half my pdf files I cannot figure it out. I use pdf files many times a day and this is really hindering my work so please please please if anyone else has experienced this or knows how to fix it that would be great thank you!!! I’m somewhat computer savvy but not completely so if you cloud please explain to me in slightly less tech terms that would be great too.

Assuming your disk is not too full, and your virtual memory settings are normal, this is not caused by software clashes, TEMP folders nor fixed by reinstalls. It is Acrobat _actually_ running out of memory, or running out of something else it has a fixed supply of.
1. Are you using any plug-ins to process files?
2. After you get this error on a particular file, restart Acrobat. Does the file now open OK?

Adobe X Pro 10.1.10 Out of Memory error message

Hello One, Hello All
Since updating our Adobe X Pro machines to version update 10.1.10, we occasionally receive an "Out of Memory" error message, which depending on what we are doing, may force us to shutdown all Adobe windows and re-open Adobe, or simply click OK and continue working with the PDF document like nothing is wrong. It seems to have no rhyme or reason to when or why it occurs. I do not see any warnings or errors in the Windows Event Log. It happens with files we have created, and also happens with files received from internal and external sources through email. It is affecting our high end machines: Lenovo X Series and W Series laptops with Windows 8.1 3rd/4th gen i5 CPUs, 8+GB RAM, 128+GB SSD's. We have all system and Windows updates applied. We have Trend Micro and Malwarebytes real-time protection and system scans do not find any malware.
I have found a few other recent threads on Adobe forum related to this error message but the responses are weak at best with no definitive fix. The system and user temp folders size are less than 100MB each so this cannot be the issue. When the error occurs I check task manager and system utilization, including memory, is well below 100%.
We did not have this issue prior to version update 10.1.10.
Really hoping Adobe can step in to help here and hoping boilerplate responses are not used.

Hi wayne103,
We released a new security update yesterday that is v10.1.11
Please update to this version and check the performance.
I have seen this error message occur while opening a 3rd party created pdf that has corrupted file structure.
Please let me know if the issue occurs for some specific files or random
Also let me know the PDF producer for these pdfs.
Regards,
Rave

Out of memory error in adobe migration tool

Hello,
While migrating data from version cue server to DAM server adobe migration tool is showing out of memory error.
Is there any way to increase memory size for migration tool.
Thanks,

Hi,
I had this issue as well. Does anyone know why this happens

Out of memory error, while using Adobe InDesign

I have been running Adobe inDesign for a couple of years with no problems. This is the first time I got a, "Out of memory" error when attempting to save the document as a PDF.
Windows 7, Dell Studio XPS, 2.80 GHz Processor, Memory: 9 GB Dram, Hard Drive: 1.5 TB, 1.56 MB cache.
Firefox v33.02
What should I do to get back the memory?
Thank you,
Don Schaaf

Hi Don, is this an Adobe site you are using in a Firefox tab, or the stand-alone InDesign application?
If it's in the application, you may want to try Adobe's forum. You also could try closing other open applications to have them release memory and then try creating the PDF again.
Please note that if Firefox has been running for a long time and is using a lot of memory, it may take several minutes to release it all, as various files are (slowly) updated at shutdown. You can monitor its progress in the Windows Task Manager on the Process tab. Press Ctrl+Shift+Esc to open the Task Manager, and then click the processes tab. Firefox will be listed under firefox.exe here. Please allow it to shut down normally instead of using the End Process button, unless it appears to hang (no movement in the amount of memory used for several minutes).

Getting 'Out of memory' error while opening the file. I have tried several versions of Adobe 7.0,9.0,X1. It is creating issue to convert PDF into TIFF. Please provide the solution ASAP

Hello All,
I am getting 'Out of memory' error while opening the file. I have tried several versions of Adobe 7.0,9.0,X1.
Also, it is creating issue to convert PDF into TIFF. Please provide the solution ASAP.

I am using Adobe reader XI. When i open PDF it gives "OUT of memory" error after scrolling PDF gives another alert "Insufficient data for an image". after clicking both alerts it loads full data of PDF. It is not happening with all PDFs. couple of PDFs are facing this issue. Because of this error my software is not able to print these PDFS into TIFF. My OS in window7*64. I tried it on win2012R2 and XP. Same issue is generating there.
It has become critical issue for my production.

Acrobat XI Pro "Out of Memory" Error.

We just received a new Dell T7600 workstation (Win7, 64-bit, 64GB RAM, 8TB disk storage, and more processors than you can shake a stick at). We installed the Adobe CS6 Master Collection which had Acrobat Pro X. Each time we open a PDF of size greater than roughly 4MB, the program returns an "out of memory" error. After running updates, uninstalling and reinstalling (several times), I bought a copy of Acrobat XI Pro hoping this would solve the problem. Same problem still exists upon opening the larger PDFs. Our business depends on opening very large PDF files and we've paid for the Master Collection, so I'd rather not use an freeware PDF reader. Any help, thoughts, and/or suggestions are greatly appreciated.
Regards,
Chris

As mentioned, the TEMP folder is typically the problem. MS limits the size of this folder and you have 2 choices: 1. empty it or 2. increase the size limit. I am not positive this is the issue, but it does crop up at times. It does not matter how big your harddrive is, it is a matter of the amount of space that MS has allocated for virtual memory. I am surprised that there is an issue with 64GB of RAM, but MS is real good at letting you know you can't have it all for use because you might want to open up something else. That is why a lot of big packages turn off some of the limits of Windows or use Linux.

Acrobat XI Pro "Out of Memory" error after Office 2010 install

Good Afternoon,
We recently pushed Office 2010 to our users and are now getting reports of previous installs of Adobe Acrobat XI Pro no longer working but throwing "Out of Memory" errors.
We are in a Windows XP environment. All machines are HP 8440p/6930p/6910 with the same Service pack level (3) and all up to date on security patches.
All machines are running Office 2010 SP1.
All machines have 2GB or 4GB of RAM (Only 3.25GB recognized as we are a 32bit OS environment).
All machines have adequate free space (ranging from 50gb to 200gb of free space).
All machines are set to 4096mb initial page file size with 8192mb maximum page file size.
All machines with Acrobat XI Pro *DO NOT* have Reader XI installed alongside. If Reader is installed, it is Reader 10.1 or higher.
The following troubleshooting steps have been taken:
Verify page file size (4096mb - 8192mb).
Deleted local user and Windows temp files (%temp% and c:\WINDOWS\Temp both emptied).
Repair on Adobe Acrobat XI Pro install. No change.
Uninstall Acrobat Pro XI, reboot, re-install. No change.
Uninstall Acrobat Pro XI Pro along with *ALL* other Adobe applications presently installed (Flash Player, Air), delete all Adobe folders and files found in a full search of the C drive, delete all orphaned Registry entries for all Adobe products, re-empty all temp folders, reboot.
Re-install Adobe Acrobat XI Pro. No change.
Disable enhanced security in Acrobat XI Pro. No change.
Renamed Acrobat XI's plug_ins folder to plug_ins.old.
You *can* get Acrobat to open once this is done but when you attempt to edit a file or enter data into a form, you get the message, "The "Updater" plug-in has been removed. Please re-install Acrobat to continue viewing the current file."
A repair on the Office 2010 install and re-installing Office 2010 also had no effect.
At this point, short of re-imaging the machines (which is *not* an option), we are stumped.
We have not yet tried rolling back a user to Office 2007 as the upgrade initiative is enterprise-wide and rolling back would not be considered a solution.
Anyone have any ideas beyond what has been tried so far?

As mentioned, the TEMP folder is typically the problem. MS limits the size of this folder and you have 2 choices: 1. empty it or 2. increase the size limit. I am not positive this is the issue, but it does crop up at times. It does not matter how big your harddrive is, it is a matter of the amount of space that MS has allocated for virtual memory. I am surprised that there is an issue with 64GB of RAM, but MS is real good at letting you know you can't have it all for use because you might want to open up something else. That is why a lot of big packages turn off some of the limits of Windows or use Linux.

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

Out of memory error - JS Runtime: How many users can one connect?

Not talking video here. Talking interactive apps, like chat. Ours crashes at about 500 connected users. When I report this I'm told "make sure you're not creating too many objects serverside" or "increase the JSRuntimeSize setting in your application.xml file to the max".
Have now done both of those things but still get this out of memory error. Let's say I optomized my app and got 100% more connection capacity. That would be 1,000 connected users - still nowhere near enough.
Are my dreams of 6,000 or 10,000 connected users enjoying all of the fruits of the FMS interactivity pipe dreams? Is it not meant for sessions of that size? Where does one find documentation or advice or application assistance on this issue?
How do large social media applications connect so many people concurrently.
Thoughts appreciated.
Thanks

Yes. I'm using the max.
<RuntimeSize>51200</RuntimeSize>
See:
http://help.adobe.com/en_US/FlashMediaServer/3.5_AdminGuide/WS5b3ccc516d4fbf351e63e3d119f2 926bcf-7ff0.html#WS5b3ccc516d4fbf351e63e3d119f2926bcf-7ed2
Don't think 100MB or 200MB would be valid settings.

Indesign cs5.5 out of memory error

Hi,
I am having constant problems with out of memory errors in indesign cs5.5 (version 7.5.3). I am on a mac. Everything is up to date, I have preflight off, my display performance is on typical view and have tried restarted my computer multiple times. I do not have any other programs open and the document I have open is 3 pages (8.5x11) with little content and a couple links to small images. I do not know what to do! This is affecting my job and my performance!! Please help!!! Thank you!

close the application
Rename the preferences from the following location
/Users/[User Name]/Library/Preferences/Adobe InDesign/Version #
/Users/[User Name]/Library/Caches/Adobe InDesign/Version [#]
then open a new document and then open the document you are facing an issue with it should clear the memory issue temporally
Alternate :
copy and paste the content in a new document and check if the 1st option does not work
PS : changing the folder name would reset the preferences
refer to KB : InDesign preferences and support file locations

Out of Memory error on some PDF's, not all PDF's.

Hi there,
I have read most of the posts in the forums that relate to 'Out of Memory' issues with PDF's and I have to say that there is still no solution that I have found.
I have tried reinstalling Adobe Reader, Flash Player and tried clearing my Temp Files. None of these fixed the issue.
The PDF's that receive this memory error are downloaded off a CMS website that has many offices and logins. Only one office is experiencing this out of memory issue so we know that it is not an issue with generating the PDF's on the CMS website, otherwise all the offices and logins would have this issue, since they use the same system.
I am an admin of that CMS website and even I receive the same out of memory issue when I try and view the PDF's from that office, as the customer does.
When we open these PDF's with another PDF reading program, the PDF's open fine. So that tells me that the issue lies with Adobe Reader and not the PDF file itself.
These PDF files that are receiving the error about 1MB-4MB, so they are not large.
Could you please tell me the solution to this out of memory error as we may lose a customer because your product is producing an error that does not seem to have been fixed after years of being reported by your customers.
Thanks.

As an Adobe Reader XI user, if I may put my two cents in, that "Out of Memory" problem is not with the Adobe Reader XI application, which was installed on our computers! I think, the problem is with how the PDF documents, which we were trying to open, were generated (or regenerated).
I remember I was able to open my old credit card statement online without any problem and now I am not able to open the same old statement (out of memory) because it could have been regenerated! In fact, I could not open any of my credit card statements (old or new) on this specific credit card web site, which makes me believe those statments were regenerated or somthing with some new Adobe software.
As others mentioned, even I'm able to view other PDF documents without any problem.

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

Out of memory errors when trying to sync local and remote sites

We cannot get our remote and local sites synchronized for the first time. We have a huge site and we get out or memory errors or the synch just doesn't work. Any solutions or insights?
Our site has 9,000+ HTML files and accompanying images, pdfs, etc. When we try to synch the remote to the local for the first time, it just will not happen. Every once in a while someone gets lucky, but for the most part, we either get an "out of memory" error or the synch just doesn't work, and it doesn't tell us anything. It just stops responding. HELP!

Hi dmooresatx,
I am not aware of the limitations of the file sizes that are allowed for a successful sync operation. If you are using a purchased version of Dreamweaver CC, send me your Adobe ID along with your contact details (phone, email number). Click on my picture and use the message option. If you are using a team license, get these details from your administrator.
Thanks,
Preran

Indesign cs5 'out of memory' error when using preflight

I have been regulary getting an 'out of memory' error when i choose to use my bespoke preflight profile.
I have 4gig of ram and run Indesign CS5 on OS 10.6.8.
Does anyone know a work around?
As soon as I select from the basic default profile, i get the beach ball from hell for 10mins, then it kindly lets me know that I am out of memory, sends a crash report to Adobe and then asks if I want to relauch. I'm stuck in a vicious circle. I must of sent my 4th crash report now and no feedback from anyone at Adobe.

I have replaced my preferences, but still the problem persists. I have tried switching my view from typical display to fast display before i selected a profile. I thought this may give me the extra memory I needed to avoid the enevitable crash. I learnt that 2 files were indeed rgb instead of cmyk before it crashed again. So I switched them to cmyk and tried again, selected my bespoke profile, but yet again it crashed. I think the problem lies with the file, not Indesign, as i have tried the same profile on a different file and the program doesn't crash and runs as it should. So if in future I need to use said crashing file again, firstly i will need to try Peter's isolate fix method. Otherwise i'll never be able to progress to successful a pdf.

Out of memory error adobe elements 3.0

Similar Messages

Maybe you are looking for