Use this forum to discuss and/or suggest future improvements of .NET Memory Profiler and to report bugs.
- Posts: 3
- Joined: Mon Apr 02, 2007 10:20 am
I'm getting an error saving a session file that contains two large memory dump snapshots.
The first snapshot is a memory dump file that's 3.7GB and the second file is 4.2GB. They took a while to load
The error dialog that pops up after some time says:
"Failed to save session file. An attempt was made to move the file pointer before the beginning of the file."
Looks like the file is too large to save? Bigger than 4GB? File pointer wrapped around?
I'm using version 220.127.116.11
- Posts: 1030
- Joined: Wed Mar 02, 2005 7:53 pm
Yes, the session file has most likely become too large. There is a 2GB session file size limit in v3.5. And, as you have noticed, the file size is not fully checked and could overflow when saving the session file, which causes the error that you are seeing. We're just about to release a maintenance version of .NET Memory Profiler 4.0 (probably tomorrow). This release has increased the session file size limit to 4GB, and will detect a file size overflow and provide a better error message. We are also changing the session file format for v4.1. In the new file format, there will no longer be a 4GB size limit.
SciTech Software AB
Users browsing this forum: No registered users and 2 guests