Big Session file (4GB) cannot be loaded

[akraus1]

Hi,

this is rather unfortunate. After waiting for about 20h to load a 4 GB 64 bit dump file I managed to see a little more what was going on. But since the profiler did eat up already 10 GB of memory I though I save the session to disk and restart the profiler. It took ages to save and exit the profiler but finally I have saved from a 3.9 GB dump file a 4.3 GB sesson file to disk.
Now I did start up the profiler a again to load the the session file but *dramatic suspense* I was immediately greeted with an OutOfMemoryException error message. How can this be? I have the 64 bit version on a really good PC with 4 Cores, Windows Server 2008 R2, 16 GB Physical RAM and tons of raid hard disk space?

Yours,
Alois Kraus

[Andreas Suurkuusk]

Even if you have a lot of RAM, there are still some memory limitations within the .NET Framework, e.g. it's not possible to allocate a managed instance that is bigger than 2 GB. A 4.3 GB session file is a very big session file and I can imagine that it can cause the profiler to allocate large managed instances.

Your problem might be caused by the memory limitation, or that something went wrong when the session file was saved. Is there any possibility that you can provide us with the session file, the memory dump, or preferably both? If it possible, please contact us at support@scitech.se, so that I can provide you with information on how to upload the files. The size of session files can usually be reduced significantly when compressing, so hopefully it will be possible for you to upload it.