A linear increase in memory usage when generating thumbnails. And predictable error at 1.8 GB.
Faulting module name: MSVCR90.dll, version: 9.0.30729.6161, time stamp: 0x4dace5b9
Exception code: 0xc0000005
Fault offset: 0x0003ae7a
Faulting process id: 0xcf8
Faulting application start time: 0x01cd4367e8cec8d4
Faulting application path: C:\XnViewMP48\xnview.exe
Faulting module path: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.6161_none_50934f2ebcb7eb57\MSVCR90.dll
Report Id: 6f1e8480-af5c-11e1-bff8-1c6f659e2078
For comparison, ACDSee 14/Pro 5 memory usage in same folder is not a linear, with maximum of 300 MB:
Also, comparison of the total load - on the left side XnViewMP (before the error), on the right side ACDSee (successful thumbnails creation). Here you can see that XnViewMP writes nothing to disk, use RAM only, and then crashes.
In test folder more than 10,000 pictures, yes I know that's a lot of data, but XnViewMP is picture manager, not an e-mail client.
Also, same thing happened with 0.39 in 2011...
All this is very sad for me.
Faulting application name: xnview.exe, version: 0.40.0.0, time stamp: 0x4fc0d2bd0.49 - crashed at 1.8 Gb RAM limit
Moderators: XnTriq, helmut, xnview
Re: 0.49 - crashed at 1.8 Gb RAM limit
Yes, Win7 x64xnview wrote:Do you have a 64bits OS?
Re: 0.49 - crashed at 1.8 Gb RAM limit
YEahxnview wrote:so XnView x64 is better... (come soon)
But this does not remove the high memory consumption.
Also, when you return to the folder with thumbnails, XnViewMP need a LOT of memory again...
Perhaps XnViewMP loads ALL thumbnails for current folder from cache to RAM, which is somewhat wasteful...
Maybe this leads to delays with file opening (http://newsgroup.xnview.com/viewtopic.php?f=60&t=25863).
Re: 0.49 - crashed at 1.8 Gb RAM limit
Yes, so you need to disable 'create for whole folder'
Pierre.
Re: 0.49 - crashed at 1.8 Gb RAM limit
You can extend the usable memory of XnView x32 up to 4gb.
Read this ("The older solution (and longer)"). It's working fine (I have no crashes at 1.8gb anymore) and is quite useful als long as we're waiting for x64 builds.
Read this ("The older solution (and longer)"). It's working fine (I have no crashes at 1.8gb anymore) and is quite useful als long as we're waiting for x64 builds.