NX2 suddenly crashes on load
After being installed for a year, NX2 started crashing on starting the program. Anyone have a similar experience?
The only change I made lately on my system was to load a piece of code for developing Apache/MySql/PHP on my desktop, but it only runs when I start those processes manually and I can't quite imagine that is the problem unless it copied an old version of some file onto my machine that NX2 is incompatible with.
#1. "RE: NX2 suddenly crashes on load" | In response to Reply # 0
Fri 04-Dec-09 12:31 AM | edited Fri 04-Dec-09 12:35 AM by MstrBones
Well, I seem to have figured out the issue.
After doing updates, reinstalling NX2 and still having the problem of crashing, I found that apparently the issue is related to the software not being able to handle its own cache file it creates.
There are two caches for NX2. One for thumbnails of images, another for whenever you edit a .nef file. My edit cache was up to 73 gigabytes and 1968 files.
I deleted it, and suddenly, NX2 is normal again. It also is much faster. I disabled caching because all it is really doing is saving some image state from where you were at in your last edit, (.nef files only), the idea being, I suppose, to get you more quickly back into an edit.
Problem is, apparently the software reads these cached editing files, or at least some portion of them, into memory when the app starts. I had notice that for months, NX2 had gotten slower and slower to start up. Finally, it had no more ability to buffer all this data. What a dumb program.
Anyway, I am back up and running.
I suggest to NX2 uses - turn off editing cache in Preferences. Your computer will thank you.
#2. "RE: NX2 suddenly crashes on load" | In response to Reply # 1
Freewheeler10 Registered since 17th Apr 2008Fri 04-Dec-09 12:56 PM
>I deleted it, and suddenly, NX2 is normal again. It also is
>much faster. I disabled caching because all it is really
>doing is saving some image state from where you were at in
>your last edit, (.nef files only), the idea being, I suppose,
>to get you more quickly back into an edit.
>I suggest to NX2 uses - turn off editing cache in Preferences.
> Your computer will thank you.
Now, here's a interesting result: when I disable the cache in NX2, it takes
longer to open an image.... with cache enabled, 1.5 seconds; with the
cache cleared and disabled more than 2.5 seconds. Using an iMac,
OS 10.6.2, CaptureNX2 2.2.3, cache is on an external Drobo array,
set for no size limit. How strange is that? Opening a previously
opened image for further editing is almost instantaneous with cache
enabled as I would expect.
Photographers' Tea: Earl 18% Grey
#3. "RE: NX2 suddenly crashes on load" | In response to Reply # 2
Fri 04-Dec-09 01:03 PM | edited Fri 04-Dec-09 02:58 PM by MstrBones
>Now, here's a interesting result: when I disable the cache in NX2, it takes longer to open an image.... with cache enabled, 1.5 seconds
Yep, that is what it is meant to do with an image that you have already edited. However, try this. Take a picture, RAW, then open and close a new image both ways. Apply no edits. It should be identical open and close, because the image is not yet cached in the Nikon cache directory.
One would have to be careful here, because the actual OS cache may have the file still in memory and skew the speeds. To properly conduct this test one would need to ensure that the file is out of memory and that might take a while, depending on how busy the system is actively reusing pages. Since all these operating systems - Mac, Windows, Unix, all use page demand virtual memory algorithms, it sometimes requires a controlled test to eliminate variables.
My point being that the caching only speeds up RAW images that you have previously edited and plan to edit again. Since I typically edit RAW images once, it has no advantage for me and only eats disk and memory resources trying to keep up with thousands of edits over time.
I should have caveated my suggestion of turning off cache with "if you only edit an image once". Even then, I'd weigh leaving it on as at least on my system, the caching was causing the startup of the program to take up to a couple minutes and using huge chunks of available memory, which I suspect in the end was what caused the crashing to start when it simply could not get enough memory for all the old files that never got looked at any more.
>How strange is that?
Not sure what you mean there...
#4. "RE: NX2 suddenly crashes on load" | In response to Reply # 3
Fri 04-Dec-09 01:05 PM | edited Fri 04-Dec-09 03:01 PM by MstrBones
>Using an iMac, OS 10.6.2, CaptureNX2 2.2.3, cache is on an external Drobo array,
What Nikon means by cache in the application is that it creates an optimized file that can return the application to its previously edited state. This caching of your steps and the images states is what over time effects the actual startup of the program, (at least in XP).
It has nothing to do with the hardware although any efficiencies of the speed of disk arrays like generic RAID or proprietary Drobo architectures and memory can help speed up processes, but then that contributes to the performance aspects of any particular machine.