e9925248
New member
On the 64 bit version I can load all "Recent" organs OK with Linear and Polyphase settings.
Linear/polyphase is a runtime setting. You can switch it without reloading.
This loads fine in the 64 bit version and un-compressed shows in GO Properties Allocated Sample Memory:-1377.906MB,
Memory Cache:0 and Max Memory Pool Size:2.184MB. The Task Manger shows GO allocated: 5,656.608 MB.
Wasn't that a 32 bit version? 2 GB max Pool size seems to indicate a 32 bit version and -1.3 GB looks like a integer overflow (if that is true, it would 2.9 GB).
In that case, you should have got a pool alloc error.
The compressed figures are 3475.555Mb, 0, 15.637Mb and Task Manger 3,656.460Mb. I do also get the odd PoolAlloc
reports but seems to run OK.
The computer has about 15GB RAM?
These numbers should not have resulted in a pool alloc error.
GO got the captibility to select the loading format for each pipe/rank seperatly (I don't remembers, if it was already present in my last 0.3.0.3 build) and tries to continue without crashing, if it rans out of memory during loading. In your case, continuing failed.Moving onto the 32 bit version.
Loading "Recent" organs seems all fine but attempting to load the larger organ fails with an AppCrash.
This occurs with No-Compression and Compression set. The failure report is as follows:
App Version: 0.3.0.5
App Timestamp: 4f3a14da
Fault Module: msvcrt.dll
Fault Module Version: 7.0.7600.16385
Fault Mod Timestamp: 425bda6f
Exception Code: c0000005
Exception Offset: 00009b60
This looks similar to the problem we saw before - see report on 25th Jan.
The Memory Allocation as given in the Task Manager for GO is 2756.752Mb
Non-compressed and 2436.564 compressed after the crash.
The MS crash information in that form is quite useless. The crash reporting tool produces some files [you can reach them via technical information in the crash dialog], which carry more information.