FAQ

Troubleshooting

It doesn't load my dump file

Firewall

MemoScope needs to load some symbols to display type names from the CLR. dbghelp.dll and symsrv.dll will try to download some files from Microsoft servers. Check your firewall settings to allow MemoScope to download files. No other access to the network will be made, trust me and check the code if you don't.

MemoScope fails to dump my process

It happens if you already have a dump file openened in MemoScope. The underlying library (ClrMd, Dbghelp) can dump only if nothing is loaded. I don't know why but I'm sure there is a good reason.

It's very slow

Performance is a feature. I coded and made all tests on my old home computer : laptop with Core i7 2630QM, 6 Go RAM and a 500 Go drive. I bought it in 2011 so it's quite old but fast enough to run MemoScope.

Is is the first time you load this dump file ?

When loading a dump for the first time, MemoScope creates a SQLite database used as a cache. So be patient, everything will be ok after.

Is the dump file on a network drive ?

MemoScope uses ClrMd and will need to access to the dump files many times so the "ping" time is very important. Save the dump files on a SSD drive is a good idea. Unfortunately I don't have one but it's still fast enough to run smoothly on my old computer.

Disk space issues

MemoScope creates a cache file (a SQLIte database) to run analysis faster. It may store a lot of data : many giga bytes, depends on your dump file number of objects and references.