ViEmu Forums - Bug in 3.0.6: Crash in Shutdown

Re: Bug in 3.0.6: Crash in Shutdown

dummy@example.com (jnothstine) — Wed, 12 Sep 2012 13:06:03 +0000

Looks like this is fixed in 3.0.8. Thanks for the fix.

Re: Bug in 3.0.6: Crash in Shutdown

dummy@example.com (Isaac_Symnum) — Mon, 03 Sep 2012 15:24:50 +0000

Apologies for the delay in answering, and for the inconveniences due to this issue. Yes, this is being addressed, and a new build will be released soon, addressing this and other issues. We expect to have it ready later this week.

Re: Bug in 3.0.6: Crash in Shutdown

dummy@example.com (zcrar70) — Mon, 03 Sep 2012 07:50:39 +0000

I have the same issue. 3.0.6, visual studio 2012.

Re: Bug in 3.0.6: Crash in Shutdown

dummy@example.com (jnothstine) — Thu, 30 Aug 2012 03:14:06 +0000

Is this being addressed? It has been up for about two weeks now and there has been no response. The problem is quite frustrating - especially when I want to make a change to visual studio and want to save it. Sometimes changes don't get saved because of the crash.

Re: Bug in 3.0.6: Crash in Shutdown

dummy@example.com (pstrjds) — Tue, 28 Aug 2012 13:17:26 +0000

Just wanted to add my 2 cents. I am experiencing the same thing since upgrading to 3.0.6.

Here is the dump from my event log:
Faulting application name: devenv.exe, version: 10.0.40219.1, time stamp: 0x4d5f2a73
Faulting module name: ntdll.dll, version: 6.1.7601.17725, time stamp: 0x4ec49b8f
Exception code: 0xc0000374
Fault offset: 0x000ce6c3
Faulting process id: 0x1778
Faulting application start time: 0x01cd70b91c11d87d
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 10.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: cd28b42d-dd76-11e1-86d8-005056c00008

Re: Bug in 3.0.6: Crash in Shutdown

dummy@example.com (jnothstine) — Fri, 17 Aug 2012 05:05:57 +0000

I have been experiencing the same problem for the last week or two. I decided to try to track down the problem tonight and narrowed it down to VIEmu. If I disable it I have no problems. If I enable VIEmu then VS crashes when I close it. I was about to start a thread on this problem when I discovered WorldMaker.

This is kind of a pain in the neck. Sometimes I have three instances of VS running and then when I want to shut everything down, they all three crash and automatically restart. If I don't edit any files then I can shut them down without them restarting.

All I have to do to get VS to crash on shutdown is to open a solution and insert some text and save the file. Then shutdown VS and it crashes.

I have ReSharper 7.0 installed. This does not seem to have an impact but I thought I would mention that I do have it.

Here is the log from my Event Viewer for the crash. I don't see it as too helpful but it is the best that I can provide.

I hope you can figure this one out quickly as it is a bit of a pain. Let me know if you want me to try anything to help track the problem down.

Thanks,

Jerry.

Faulting application name: devenv.exe, version: 11.0.50727.1, time stamp: 0x5011ecaa
Faulting module name: ntdll.dll, version: 6.1.7600.16915, time stamp: 0x4ec49d10
Exception code: 0xc0000374
Fault offset: 0x000ce903
Faulting process id: 0x1b58
Faulting application start time: 0x01cd7c3415a7cd80
Faulting application path: C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id: f247a120-e827-11e1-8d5b-545b3b9ecd0d

Bug in 3.0.6: Crash in Shutdown

dummy@example.com (WorldMaker) — Thu, 16 Aug 2012 20:40:34 +0000

I'm seeing this behavior in both VS2010 and VS2012 with ViEmu 3.0.6 installed: every time, or just about every time, I close/shutdown Visual Studio, just after the main window disappears, it gives a crash box with no details at all and restarts Visual Studio. In some cases, it also happens early enough in Visual Studio's shutdown process that some window placements/settings are not properly restored.

Closing a Solution, but leaving the IDE itself running, does not appear affected, and is part of my current workaround to at least avoid some of the worst things like window/settings forgetfulness.