HomeSeer Technologies LLC
If you still experience problems there are some standard troubleshooting you can perform:
Disable root referee identification
Under .NET Framework 1.x, root referee identification starts an additional AppDomain. This causes problems for some application, especially if it uses dynamic application domains. And in .NET Framework 2.0 there is a bug in the framework which may cause problems when collecting a snapshot (we have written a workaround for this bug, and according to our tests it works well).
Disable the dispose tracker
The dispose tracker should work without any problems, but it does add some complexity to the profiled process (e.g. it modifies the IL code of the program).
If you still have problems collecting snapshot, you can provide us with additional information by sending us log files.
To create the log files you must supply the "/log" command line argument to the profiler executable (NetMemProfiler.exe). This will create three log-files in the program directory: ProfilerLog.txt, ProfilerClientLog.txt and AssertLog.txt (AssertLog.txt will probably be empty). If you send these log files to email@example.com (preferably zipped), it will give us more detailed information about your problem.[/list]
SciTech Software AB
Users browsing this forum: No registered users and 21 guests