OutOfMemory exception on Windows Vista

Hello Johnny

thanks for letting us know. We are not aware of any known memory leak issues, would it be possible for you to send us a (mini) crash dump if it occurs? Does this happen on other computers running this configuration?

Also, are there any additional addins running in your Visual Studio, such as ReSharper?

Thanks!

Hello Igal,
Sorry for the delay (we're currently releasing a new version of our software).

An addition to my initial posting: We currently develop only with Visual Studio 2008. My last sentence referring to VS2010 was a mistake. It should be VS2008.


The additional addins we run are VisualSVN (all), TestDriven.Net (nearly all) and ReSharper (only one). There is no difference for the OutOfMemory Exception in Debug-mode of Visual Studio. In that case we get the exception from the .Net Framework itself, so we don’t have a crash dump.

The Visual Studio crashes are a bit more depending on the machine. The one with ReSharper installed only crashed one a week, others one a day and one up to 4 times a day. After a restart
of the Studio all works good until the next reboot.


We currently try to reproduce the Problem with a simple ASP.net solution.

Do you have a link how we could produce a mini crash dump? So far we never needed such a thing and maybe you have a little guide for that task.

Thanks.
Johnny Graber

Hi,

You have two options to create a mini dump:
Option one: Use adplus.vbs from debugging tools for windows package to create the dump:
Download the package from here:
http://www.microsoft.com/whdc/devtools/ ... 6.mspx#EHD
I suggest you choose version 6.11.1.404 this is not the latest version but the download size is smaller. Also you if the crashing process is 64 bit download the x64 version else download the x86 of course :)
after the installation run the ADOlus.vbs script from the command line
<DebuggingToolsInstallationFolder>ADPlus -hang -pn CrashingProcesName.exe
This will create a folder in the Debugging tools installation folder with name in the form Hang_Mode__Date_xx-xx-2010__Time_xx-xx-xxx
Inside the folder you can find the dump file.

The other option is to change your system default postmortem debugger to Dr. Watson. See the details here:
http://msdn.microsoft.com/en-us/library/ff542967(VS.85).aspx
look at the section that starts with:
"To change the postmortem debugger back to Dr. Watson, run drwtsn32 -i."
Use this method only if you know how to change it back to the settings that visual studio set for you when you installed it.

Please let me know if you need more help generating the dump.