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.

Similar Messages

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.

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.

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

Photoshop keeps on getting out of memory error after installing Premier Pro

I just upgrade my CS to CC. Yesterday I installed Photoshop and did my work without any problem but today after installing Premier and After Effect, I keep on getting out of memory error when I'm working even though I don't have any other application running accept photoshop alone. The file I'm working on is a small file, iphone plus size interface. Basically I can open the file, add blur effect and try to type text I will get photoshop telling me that my system is out of memory. Restarting photoshop give the same problem, restarting my computer give the same problem, ie do one thing and next will give memory not enough.
I don't think my system is slow as it is workstation with dual processor and 12 gig of ram, windows 7 64bits 1gb dedicated memory for graphic card.
I uninstall Premier and After Effect and suddenly the problem go away. Photoshop work as per normal. I didn't have the time to reinstall premier again but will try to do it tonight or tomorrow
Anyone experience such problem before?

When you get that error leaver the error showing and use something the can show you how much free disk space there is left on Photoshop scratch disk. It may be a problem with scratch storage space not ram storage space. I see Photoshop use much more scratch space the ram. I have seen Photoshop using less than 10GB of ram on my machine leaving 30GB of free ram on my system unused while using over 100GB of scratch space.

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

FCP - Out of Memory Error in 10.6.6

Running a MacBook Pro 17" (A1261) and while I edit, I got a "Out of Memory" Error and an "Invalid Operation". Can't reopen the sequence on my MacBook but it opens with no problem on a Mac Pro.
Gonna re-install the OS and see if that helps.

I just had something very similar happen. A sequence that I've been editing for over a month now no longer opens (since installing the 10.6.6 update) I'm getting the same "out of memory" and I/O error codes.
I'm at a loss what to do. Other editing projects open fine. But so far I haven't been able to open
any of the project files I've vaulted from the last six weeks.
Does anyone have any idea what changes 10.6.6 might have made to cause this and how
it could be rectified. I really need to get back into my project file.

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.

HELP out of memory error message

I'm using fcp 7 with 10.6 on a macbook pro.
I just finished editing a 16 minute photo montage with about 100 stills. The pictues all of movement.
I used some of the pictures in photoshop and AE.
When I try and render I'm getting "out of memory" error. All of the footage is on my 1 tb external hard drive with
450 gig not used. I've done more layered ones before with no issues.
I tried to render indivdual clips and several clips. It worked fine for a while. The render files are about 7 gig
so it's not much. I also tried to output the whole sequence instead of rendering and I'm still getting the
"out of memory" I need to output by tomorrow.
Thanks,
Michael

I have done some Google searching, and FCP 7 is a 32-bit application. So it is my guess that whatever you are currently doing has FCP 7 wanting to use more than 4 gigibytes of Virtual Address space, and it cannot grow expand any further because it is a 32-bit applications.
This is my best guess as to why you are getting "out of memory" errors.
I am not an FCP user so I cannot suggest any tricks to get this to work. The only other suggestion is to get newer version of FCP which is 64-bit capable, but that might also require upgrading to a newer version of Mac OS X, so going down the upgrade road can get involved.

Out of memory error - WLW Schema Project build

hi
Wasn't sure which group (workshop vs xmlbeans) but here goes.
I'm doing a persomal eval of the WLS 8.1.1. platform.
My current focus is on XML Schema support, XML Beans, transformations etc
and in particular how it all copes with large schema.
I'm using Justice XML Data Dictionary (3.0.0.0) as an example of a large
schema
(http://it.ojp.gov/jxdd/)
I am getting an out of memory error when I build this within WLW.
The build appears to be in the javac phase (and occurs when the memory goes
over 256M) so I think it's the ANT task.
WLW doesn't seem to be running out of memory and the build machine is not
running out of resources.
Where do I configure this? The <xmlbean> tag ? Is there any doco?
regards
Jim Nicolson
=============== Build trace below ====================
Build project JXDDSchema started.
BUILD STARTED
build:
check-uptodate:
build-sub:
Updating property file:
C:\data\projects\bea\integration\wlitest\.workshop\.ide\JXDDSchema\build.pro
perties
Deleting directory
C:\DOCUME~1\JIMNIC~1\LOCALS~1\Temp\.wlw-temp\wlw_compile38940\JXDDSchema
Created dir:
C:\DOCUME~1\JIMNIC~1\LOCALS~1\Temp\.wlw-temp\wlw_compile38940\JXDDSchema
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\jxdds_3.0.0.0_full-doc.x
sd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_639-2t_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ut_offender-tracking-mis
c_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-gun_1.0.0.0_fu
ll-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-other-transact
ions_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-uniform-offens
e_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\mn_offense_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\dod_jcs-pub2.0-misc_1.0.
0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\cap_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\nibrs_misc_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\fips_6-4_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_3166_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\dod_misc_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-misc_1.0.0.0_f
ull-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-boat_1.0.0.0_f
ull-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-securities_1.0
.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-article_1.0.0.
0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\unece_rec20-misc_1.0.0.0
_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-state-country_
1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_4217_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\fips_10-4_1.0.0.0_full-d
oc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ansi_d20_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\iso_639-2b_1.0.0.0_full-
doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\fips_5-2_1.0.0.0_full-do
c.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-vehicle_1.0.0.
0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\dod_exec-12958_1.0.0.0_f
ull-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\ncic_2000-personal-descr
iptors_1.0.0.0_full-doc.xsd
Loading schema file
C:\data\projects\bea\integration\wlitest\JXDDSchema\usps_states_1.0.0.0_full
-doc.xsd
Time to build schema type system: 6.75 seconds
The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError
BUILD FAILED
BUILD FAILED

hi Kevin
Thanks I'll take a look there.
I think it's a good move to make XMLBeans open source.
(I've been using Castor for the same purpose for the last two years).
I was mainly focussed on XMLBeans as they are used in WLW context and my
testing suggested that I would probably want to know more about the ANT
build/tasks etc. (Just to be able to deal with unexpected issues)
It's not urgent - I'm just doing a personal eval to come up to speed with
WLS 8.1 platform.
thanks
Jim Nicolson
"Kevin Krouse" <[email protected]> wrote in message
news:[email protected]..
Sorry, the first URL should have been:
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-xmlbeans/v1/xkit/anttask.html?rev=1.2
>
--k
On Tue, 30 Sep 2003 22:35:58 -0700, Kevin Krouse wrote:
Hi Jim,
Well, the XMLBean docs are in a process of moving into the Apache
XMLBeans
project (http://xml.apache.org/xmlbeans), so I can point you to where
they
are in the cvs repository. You can also look at the source if you'dlike!
>>
Here's an html doc for the xmlbean task:
http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-xmlbeans/v1/xkit/anttask.html?rev=1.2http://cvs.apache.org/viewcvs.cgi/*checkout*/xml-xmlbeans/v1/xkit/anttask.html?rev=1.2
>>
Here's the code for the xmlbean task:
http://cvs.apache.org/viewcvs.cgi/xml-xmlbeans/v1/src/xmlcomp/org/apache/xmlbeans/impl/tool/XMLBean.java?rev=HEAD&content-type=text/vnd.viewcvs-markup
>>
>>
As to your second question about WLW becoming unresponsive, after the
Schemas.jar is built, the source for the entire project is re-scanned
which could take several minutes. The performance impact of rescanning
the project is improved in SP2 and will be addressed even more in future
releases. Stay tuned.
--k

Out of Memory error after upgrading to Reader X

We have several PDF documents that work fine on Reader 9. But after upgrading to Reader X, the files will not open. Instead, they report an Out Of Memory error and a blank document opens instead. Removing Reader X and re-installing Reader 9 corrects the issue. This has been reproduced on 3 different PCs running both Windows XP and Windows 7.
Any suggestions?

Just to throw in my 2 cents... Adobe has known about the out of memory bug at least since 01/12/2011 because that is when I reported the problem to them. I even had an escalated support case #181995624 and bug#2800823. Our problem comes from a EFI Fiery E7000 attached to our Lanier LD460c Copier. Any pdf's made from that copier will not open in Acrobat X, although they will open in lower versions of Acrobat just fine. Our only workaround is to keep Acrrobat 9 on office computers, or you can open the offending pdf in Acrobat 9 or earlier and print it to pdf, and then it will open in Acrobat X!!! They acknowledged that this was a bug, see my email chain below. This was the last update I received from Adobe, very frustrating...
From:
Sent: Wednesday, February 09, 2011 9:12 AM
To:
Cc:
Subject: RE: Case 181995624; Unable to open PDF
Hi Phil,
We do not have this information or estimate time by our Engineering team yet.
Regards,
Neeraj
From:
Sent: Monday, February 07, 2011 8:19 PM
To:
Cc:
Subject: RE: Case 181995624; Unable to open PDF
Next major release as in the next patch for Acrobat X, or as in Acrobat 11?
From:
Sent: Saturday, February 05, 2011 4:31 AM
To:
Cc:
Subject: Case 181995624; Unable to open PDF
Hi Phil,
You can get back to us with the Bug Number provided you earlier based on which we will give you the update by our Engineering team. However, the update for now is that it is decided to fix in our next major release.
Regards,
Neeraj
From:
Sent: Thursday, February 03, 2011 1:33 AM
To:
Subject: RE: Case 181995624; Unable to open PDF
Can you send me a link to where I can find information on the bug?
From:
Sent: Tuesday, February 01, 2011 10:14 AM
To:
Cc:
Subject: Case 181995624; Unable to open PDF
Hi Phil,
Hope you are doing well.
I have researched on your issue and found that it is a BUG with Acrobat X. I have logged it on your behalf so that our Engineering team can have a look on that. Please find the Bug Number #2800823 for any update on this in future. I am closing this case on your behalf.
Have a nice day.
Regards,
Neeraj
From:
Sent: Tuesday, February 01, 2011 12:22 AM
To:
Cc:
Subject: RE: Case 181995624; Unable to open PDF
Any updates on this case?
From:
Sent: Friday, January 14, 2011 2:03 PM
To:
Cc:
Subject: RE: Case 181995624; Unable to open PDF
The EFI Fiery E-7000 Controller version is 1.2.0 and it handles the scanning and printing functionality of our Lanier LD160c copier. I have attached two sample files. One is a 1 page scan from our copier. The other is a combined pdf that I just created in Acrobat 9. The first two pages of the combined pdf consists of a webpage that I printed using Acrobat 9 and then the scan from the copier is on the 3rd page. In Acrobat X, once you get to the 3rd page you will receive the Out of Memory error. It will open in previous versions of Acrobat just fine though.
From:
Sent: Friday, January 14, 2011 11:52 AM
To:
Cc:
Subject: Case 181995624; Unable to open PDF
Hi Phil,
Thanks for the information.
I have the PDF file provided by you and able to reproduce the behavior. I tried to call you at 214-303-1500 but got voice mail.
Please let me know when you will be available so that I could call you and continue further with this issue.
Regards,
Neeraj
From:
Sent: Thursday, January 13, 2011 6:57 AM
To:
Cc:
Subject: Re: Case 181995624; Unable to open PDF
It is a walk up copier and we scan to email. The EFI Fiery controller E7000 handles pdf conversion for the copier, but yes it has the latest firmware. The bottom line is that we have 3 or 4 years worth of pdfs created from that copier rendered useless by Acrobat X. They open fine in previous versions of Acrobat. Did you get the test pdf file when this case was created?
-- Sent from my Palm Pre
On Jan 12, 2011 6:12 PM, Acrobat Support <[email protected]> wrote:
Hi Philip,
Thank you for choosing Adobe Support we have got your concern, we see that you are facing an issue with opening PDF files in Acrobat X, created from Lanier (Ricoh) LD160c copier. A technical support case 181995624 has been created for your reference. In order to assist you further. We would like to have the following information.
· Are you using the latest scanner driver ?
· What is the exact scanning workflow ?
Regards
Acrobat Support

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

Out of memory error on Final Cut Express

Hello,
Ok so quite often we have to record into iMovie6 live (on a Macbook Pro) so that we can get all the content being recorded without gaps (tapes don't last long enough). After the project is imported (and transfered to my Powermac with FCE on it) I would rather use Final Cut Express to edit everything. So after saving the iMovie project I start a new project in FCE and import the files from iMovie. When this happens the audio always needs rendered and often when I render these files it really bogs down my PowerMac G5 and eventually gives me an out of memory error. After looking at Activity Monitor during the rendering, the System Memory just starts to become inactive and then eventually active until all the memory is used. That's usually when I get the memory error in FCE. I have 1GB of memory and I've added another Gig but the result is the same. It appears this is a problem with the app. Anyone have a clue or any ideas? I am using Final Cut Express HD 3.0.1 on my PowerMac.
Thanks-
Adam

Thanks for the comments however I currently have a project that I am trying to get done and these comments don't help right now. Anyone have any advice to speed up the process?
I just need to render the audio faster without having to reboot all the time. Any other FCE project works fine when rendering audio, it's just the import from iMovie that for some reason soaks up my memory and causes me to have to reboot to get it back.
Thank you-
Adam

"out of memory error" message when not out of memory

I've gotten this message before (as have others) when I'm clearly not out of memory. It's been about a year since this happened last, and I can't remember how I solved it. It seems many others have had this problem and that there has been no simple solution. It occured when I was trying to revise some titles over an imported .mov image which was downloaded from the internet. I revised the titles, but they wouldn't render. Then I got the "out of memory" error message. So far I have:
1) Logged out and logged back in
2) Rebooted
3) Pasted my sequence into a new sequence
4) Saved the project as a new project
None of these things have worked. Of course this all happens when I'm at the very end of the project with a deadline of tomorrow.

I'm having the same problem. I searched "out of memory" and found this solution on another thread..
http://discussions.apple.com/thread.jspa?messageID=1162802&#1162802
However, it didn't help me and I am still looking for an answer. I am running FCP HD 4.5 and Avid Express Pro. I edidted together an 18 min video w music, no effects and exported it as a reference movie. Imported to FCP to add chapter markers and that's when I get the "General Error Out of Memory" Tried the make clip offline thing, but that didn't work. Tried exporting a different video from Avid, 3 min and that worked (with chapter marks).
Anyway, I feel your pain. If you find a solution, please mark this thread "question answered"
Thanks
Quicksilver 867 Mac OS X (10.3.9) 1.12 GB SDRAM, 80 gig + 160 gig

RoboHelp 9 gives an out of memory error and crashes when I try to import or link a Frame 10 file or

I have Tech Suite 3. If I start a new RoboHelp project and try to import or link Frame files, RoboHelp tries for a while, then I get an Out of Memory error and the program crashes.
I opened one of the sample projects and was able to link to one of my frame files without any problem, so it seems to be an issue with creating something new.
Any suggestions?

It happens when I create a new project and then try to import or link frame docs to make up the content. It starts scanning, then crashes. I did get it to the conversion setting page once, but no further.
It does not happen if I open one of the supplied example projects and link a file. But then it doesn't let me choose, during import, any style mapping. And I can't delete the sample project fold
Twice now it has told me when I tried to import (not link, but import) that my .fm file could not be opened, and told me to verify that Frame is installed (it is) and that the file is a valid frame file (it is).
The docs and project are in separate folders on my C: drive.

Acrobat XI Pro "Out of Memory" Error.

Similar Messages

Maybe you are looking for