-
crashing due to real memory allocation overload
We are having an escalating crash problem when working with big final cut projects (200MB). The activity monitor seems to indicate the strange behaviour is regarding real memory allocation.
If one project is open, the final cut allocates about 1.6GB real memory and works fine. After opening another big project (or when rendering in process), FCP allocates more and more memory and when the real memory reaches 2GB the number changes to 16,777,216.00TB!
Final Cut becomes very unstable and crashes. Sometimes it crashes when reading project, sometimes when playing sequence or during rendering, its behaviour is random. Crash report might be displayed, but not every time.
Everything runs on MacPros 2xDual 2.66GHz, 4GB RAM (the same behaviour can be observed on three identical machines). The issue occurs either when working with media files on Xsan shared volume or with media located on internal disk.
Any ideas? Thanks for the help.
-
6 Replies
-
16 million TB’s of RAM is impressive
Large project files have always been problematic. My last one around 230 was extremely crashy – and I certainly couldn’t open more than 1 project at that rate.
1) try changing your Prefs for system memory usage. Try 87% for application (the old Combustion trick)
2) pare down that project file. Save a copy that only contains the sequence or sequences that are needed. No clips in bins, nothing. All that junk gets loaded up and can bog things down.
-
Exactly the same number for me!!!
16,777,216.00TB of real memory on my system too!!!Strange to have the same number on both systems for sure. I have the original 4×512 sticks of ram from Apple and another 4x1GB sticks from DMS Memory. I can render with just the Mac installed memory. I remember back in the old days that Apple released a software update that reported other manufacturers ram as bad, they were told “that’s a NO! Bad dog!” by the government powers that be. Do you think Apple is writing code again that wrecks third party ram and tells the system that it’s junk.What is going on. I have been through three sets of ram from DMS and they do not know what is going on either. Strange things are afoot.
Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4
-
The firmware update from Apple that caused ram problem checked ram for timing compliance. The memory that failed did not run at the faster speeds required in the new firmware, or was not able to report that it was capable (and thus wouldn’t have run at that higher speed).
There was no malicious code based on ram manufacturer. There was only code with a query to detect ram that could not operate in the higher speed mode required by the firmware.
I’m not sure about your Final Cut issues, but I’ve had problems with large projects in the past, so I always keep them pared down.
-
Edit: After the latest Apple update, I am able to render my minuscule timeline with only the Apple Ram (2gb). I will re-install the DMS memory and test for all of you who are having this problem.
////////////////////////////////
Thanks for the update on the software update.
So Apple DID do it!
Oh that’s right, you didn’t disagree:)On the subject again.
My project is only 3 minutes long and the FCP filr is only around 2.5 MB. I still get the HUGE ram usage and then crash after crash.Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4
-
You listed FCP 5.1.4.
Which version of quicktime are you on? Perhaps your quicktime version is not compatible with the older FCP.
-
I’m on Quicktime 7.3.1.
Good, bad, indifferent?
I have just had luck with rendering with third party ram. I still see 16,777,216.00 TB of ram usage. Very strange. I am having some troubles with DVD Studio Pro now. It may be time for a system rebuild. I also have Windows XP installed via bootcamp. I will probably say good bye to that as only Leopard has Bootcamp support.
Dual Core 2 Duo 3.0Ghz, 6GB ram, 2x500GB Raid, Tiger 10.4.11, FCP 5.1.4
Reply to this Discussion! Login or Sign Up