Visual Studio Crash in Win 10

[MikleF]

Hi,

We are currently trying to supply linked clone desktops for our Developers.

They have come to me with a problem that they cannot leave their VDI to compile their solution overnight.

It seems that when they reconnect after some time while visual studio is still open it just crashes when they get in their VDI.

Anybody had this issue as well ?

FYI we are talking about Visual Studio 2013 on Win10 machines.

[grossag]

Are you able to get a dump from the crashed Visual Studio instance? Sometimes Windows will create one depending on the version; if not, I tend to use procdump to grab a dump of the crashed process.

That may help us isolate whether it is any of our interception components causing a crash.

[davidvr]

I have the same issue and it can also be recreated with SQL Server Management Studio by running SSMS then disconnecting and then reconnecting to VDI some time later. Here are the errors I get:

Log Name:      Application

Source:        Application Error

Date:          10/4/2016 11:35:20 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Description:

Faulting application name: Ssms.exe, version: 2015.130.15600.2, time stamp: 0x57852eb9

Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f3b2a

Exception code: 0xe0434352

Fault offset: 0x000b3e28

Faulting process id: 0x4368

Faulting application start time: 0x01d21e4c7d54e90c

Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\Ssms.exe

Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll

Report Id: 45eb8fb8-3ca3-4052-8756-2bbe13f3f027

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-10-05T04:35:20.000000000Z" />

    <EventRecordID>62873</EventRecordID>

    <Channel>Application</Channel>

    <Security />

  </System>

  <EventData>

    <Data>Ssms.exe</Data>

    <Data>2015.130.15600.2</Data>

    <Data>57852eb9</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>10.0.10240.16384</Data>

    <Data>559f3b2a</Data>

    <Data>e0434352</Data>

    <Data>000b3e28</Data>

    <Data>4368</Data>

    <Data>01d21e4c7d54e90c</Data>

    <Data>C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\Ssms.exe</Data>

    <Data>C:\Windows\SYSTEM32\KERNELBASE.dll</Data>

    <Data>45eb8fb8-3ca3-4052-8756-2bbe13f3f027</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Log Name:      Application

Source:        Application Error

Date:          10/4/2016 11:35:20 PM

Event ID:      1000

Task Category: (100)

Level:         Error

Keywords:      Classic

User:          N/A

Description:

Faulting application name: Ssms.exe, version: 2015.130.15600.2, time stamp: 0x57852eb9

Faulting module name: KERNELBASE.dll, version: 10.0.10240.16384, time stamp: 0x559f3b2a

Exception code: 0xe0434352

Fault offset: 0x000b3e28

Faulting process id: 0x4368

Faulting application start time: 0x01d21e4c7d54e90c

Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\Ssms.exe

Faulting module path: C:\Windows\SYSTEM32\KERNELBASE.dll

Report Id: 45eb8fb8-3ca3-4052-8756-2bbe13f3f027

Faulting package full name:

Faulting package-relative application ID:

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Application Error" />

    <EventID Qualifiers="0">1000</EventID>

    <Level>2</Level>

    <Task>100</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-10-05T04:35:20.000000000Z" />

    <EventRecordID>62873</EventRecordID>

    <Channel>Application</Channel>

    <Security />

  </System>

  <EventData>

    <Data>Ssms.exe</Data>

    <Data>2015.130.15600.2</Data>

    <Data>57852eb9</Data>

    <Data>KERNELBASE.dll</Data>

    <Data>10.0.10240.16384</Data>

    <Data>559f3b2a</Data>

    <Data>e0434352</Data>

    <Data>000b3e28</Data>

    <Data>4368</Data>

    <Data>01d21e4c7d54e90c</Data>

    <Data>C:\Program Files (x86)\Microsoft SQL Server\130\Tools\Binn\ManagementStudio\Ssms.exe</Data>

    <Data>C:\Windows\SYSTEM32\KERNELBASE.dll</Data>

    <Data>45eb8fb8-3ca3-4052-8756-2bbe13f3f027</Data>

    <Data>

    </Data>

    <Data>

    </Data>

  </EventData>

</Event>

Log Name:      Application

Source:        .NET Runtime

Date:          10/4/2016 11:35:20 PM

Event ID:      1026

Task Category: None

Level:         Error

Keywords:      Classic

User:          N/A

Description:

Application: Ssms.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.OutOfMemoryException

   at System.Windows.Media.Composition.DUCE+Channel.SyncFlush()

   at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1<ChannelSet>)

   at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)

   at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)

   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name=".NET Runtime" />

    <EventID Qualifiers="0">1026</EventID>

    <Level>2</Level>

    <Task>0</Task>

    <Keywords>0x80000000000000</Keywords>

    <TimeCreated SystemTime="2016-10-05T04:35:20.000000000Z" />

    <EventRecordID>62872</EventRecordID>

    <Channel>Application</Channel>

    <Security />

  </System>

  <EventData>

    <Data>Application: Ssms.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.OutOfMemoryException

   at System.Windows.Media.Composition.DUCE+Channel.SyncFlush()

   at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1&lt;ChannelSet&gt;)

   at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)

   at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)

   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

</Data>

  </EventData>

</Event>

[ccairns]

I experience this problem daily in both Visual Studio and SQL Server Management Studio on Windows 10 in VMware Horizon.  Each instance of those apps will crash when I reconnect after being out of a session for a while.  I'm glad to finally have confirmation that it is a flaw.  I hope VMware will work with Microsoft to get this resolved.

[needanswersnow]

Hi,

Just wondering if anyone ever opened a case with VMware on this issue? Would you have a case reference?

Thanks.

[Maarten_Caus]

Hi,

I have the exact same problem on Windows 10 persistent machines with Visual Studio version 2015 update 1 professional and 2013 premium.

We are running View 7.0.2. What version are you using?

I have an active case for this problem and will update accordingly.

Have any of you found the exact amount of time when this issue accurs. I know it's at least 2.5 hours.

Kind regards,

Maarten

[dolphan757]

Has anyone found an resolution to this issue? We are having the same exact problem with our developers having their VS 2015 cash in their Win10 VDI. 

[dakm4]

We are also having this issue with Visual Studio. Are there any updates on the VMware ticket that may be helpful? We are not in production yet but have seen this issue seen in our testing.

[prechtj]

We've had a case open since November with the developers looking into it - we were able to reproduce on 6.2.2 and 7.0.0 on Windows 10. Same issue with SQL Server Management studio - our developers will start a query, disconnect, and on reconnect back the desktop will crash with the app event listed above in this thread in the Windows logs.

[Maarten_Caus]

I have case open since september or august with the development and haven't found the cause of the problem.

We tested it on Windows 8.1 and than the Visual Studio does not restart on a reconnect after 4 hours.

Can we exchange information to push this problem forward?

Kind regards,

Maarten

[Maarten_Caus]

Hi,

The development team reached back and concluded it's a Windows problem:

Here are the steps that we have performed on a Physical PC:

- Install Visual Studio 2015 on a Physical PC
- Launch Visual Studio
- Open cmd, use tsdiscon ( It will lock the system )
- Leave PC idle for nearly 6 hours
- After 6 hours, when we log in back and keep mouse cursor focus on VS 2015, we get a prompt stating Visual Studio 2015 Stopped Working

We have performed this test for 3 times and it crashes on every instance.

Kind regards,

Maarten

[vemacz]

Hi,

I can confirm. The only way when it won't crash is when user is connected via RDP protocol. When user is connected via PCoIP or directly to console and use tsdiscon, after 6 hours it'll crash.

[MikleF]

Interesting to see this is also an issue on physical machines.

I operated under the assumption (based on feedback from the programmers) that this was not an issue in the current environment.

What did you guys do with this info? Did you open a case at Microsoft?

[Maarten_Caus]

Hi Mike,

Yes, I had a case open with Microsoft and VMware. Microsoft says that they can't reproduce the problem with the steps provided.

When everyone else can. Our costumer is pushing Microsoft to look into this. I will update the post when I have more information.

KInd regards,

Maarten Raido

[chriskumm]

Hello I am a TSE on the Horizon View team.  Can you provide me with VMware SR# you are working out of?  I want to see if I can get this moving on the back end.

[Zleipner73]

Hi,

Did you ever figure this one out? We're seeing the same exact issue in our Windows 10 / Horizon 7.0.2 environment.

SSMS 17.4 (also tried 17.5 and 17.6 but not 17.7 yet), Visual Studio 2015.

Faulting application name: Ssms.exe, version: 2017.140.17213.0, time stamp: 0x5a1dcb4d

Faulting module name: KERNELBASE.dll, version: 10.0.14393.1770, time stamp: 0x59bf2bcf

Exception code: 0xe0434352

Fault offset: 0x000daa12

Faulting process id: 0x2090

Faulting application start time: 0x01d3fcf1ec8bac98

Faulting application path: C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe

Faulting module path: C:\Windows\System32\KERNELBASE.dll

Report Id: 4a38f383-9b7f-41be-a4a5-6b71bcb5a5db

Faulting package full name:

Faulting package-relative application ID:

Application: Ssms.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.OutOfMemoryException

   at System.Windows.Media.Composition.DUCE+Channel.SyncFlush()

   at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean, System.Nullable`1<ChannelSet>)

   at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr)

   at System.Windows.Interop.HwndTarget.HandleMessage(MS.Internal.Interop.WindowMessage, IntPtr, IntPtr)

   at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)

   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)

   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)

   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)

   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)

   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)

   at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr, IntPtr, Int32, IntPtr, IntPtr)

   at System.Windows.Forms.NativeWindow.DefWndProc(System.Windows.Forms.Message ByRef)

   at ApexSql.SourceControl.Ssms.WrapperClasses.MainWindowSubClass.WndProc(System.Windows.Forms.Message ByRef)

   at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr, Int32, IntPtr, IntPtr)