VS 2012 crash after 2012 Q3 upgrade on Windows 8 (also on Windows 7 and VS 2010)

[Jeff]

Computer: Windows 8, 64-bit, 8GB RAM

I upgraded my DevCraft 2012 Q2 SP2 installation to Q3 today and and VS 2012 is crashing after opening a solution.  I have the following components installed:

• RadControls for WinForms
• RadControls for ASP.NET AJAX
• RadControls for WPF
• RadControls for Silverlight
• KendoUI for ASP.NET MVC
• MVC UI Extensions
• Reporting
• JustTrace
• OpenAccess
• JustMock

After installing, I started VS 2012 and took a very long time (perhaps 20 minutes) to get to a responsive state.  I watched it in Task Manager and it looks like one core was pegged at 100% during this time and RAM consumed grew to over 500MB.

VS did come back eventually and I loaded a solution.  Everything looked for a few seconds and then visual studio crashed.  I tried rebooting and restarting VS but it crashes every time I try to load a solution.  I went into the Windows EventLog and found this error:

Application: devenv.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Exception
Stack:
at System.Windows.Application.LoadComponent(System.Object, System.Uri)
at Telerik.VSX.Shell.Xaml.CommonXaml.InitializeComponent()
at Telerik.VSX.Shell.VSWindow..ctor()
at Telerik.VSX.Forms.BaseNotificationForm..ctor(System.IServiceProvider)
at Telerik.VSX.Helpers.NotificationManager..ctor(System.IServiceProvider)
at Telerik.KendoUI.Mvc.VSPackage.VsPackage.GetUpgradeAvailabilityMonitor()
at Telerik.VSX.VSPackage.PackageBase+<>c__DisplayClass5.<OnSolutionOpened>b__2()
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(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 MS.Internal.Threading.ExceptionFilterHelper.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)

I then restarted VS and instead of loading a solution, I tried running TELERIK\VS Extensions Options...  This also failed with a dialog complaining about a missing resource (see the attached image).

I also installed the update on a Windows 7 64-bit machine with both VS 2010 and 2012 installed.  VS 2010 did not have the excessively long startup time but it also crashed when I tried loading a solution.  VS 2012 seems to be stuck loading a solution right now.

Looks like something is wrong with Kendo.  I'm going to try uninstalling it.

While uninstalling all of the Kendo components on my Windows 8/VS2012 machine, I went over to the Windows 7 machine, launched VS 2012 and opened the Telerik\VS Extensions Options...  I didn't get an error message this time but the dialog is messed up.  See the attached image.

Update: After uninstalling all of the Kendo components on the Windows 8/VS 2012 machine, VS2012 was able to load a solution and work normally.  On the Windows 7/VS2010 machine, I'm now seeing VS2010 crash whild loading a solition.

[Yong Gu Kang]

Hi,telerik

I had same problem with Jeff at VS 2010,in which my project have about 40 more SL5 project
and 1 kendo UI Mobile project with Q1 2012.
Upgrade process of Q3  looks much advanced but still half baked,I had to manually update abt 20 projects more,
especially telerik.Reporting component for SL5 not showing at Add-Reference.

After upgrade including just-code/mock which I have never used, and whole re-compiling, at first a few times I can run project
but takes so long time to load whole project,it took long time to  load toolbox which was not happened at Q1 2012.
Finally I removed registry key of toolBox and removed just-code/mock and even put off Open-Access start up in VS option,
and then loding runs very fast, however, always crashed after loading whole projects and can't get error messages or
something else bcz VS debbuger instance also crashed repetedly.
I had no way to remove and re-install VS2010 , but still no luck.

After spending this afternoon, I moved first time into VS2012 and can catch same error message with Jeff  in vs 2012 debugger
as attachaed image. My dev machine is Win7/32bit and 4GB RAM.

Update : I removed installed Kedo-web/UI/MVC except kendo mobile and datawiz.
              The copy of script files of Q1 2012 still resides in my web project and runs fine in VS 2012/Win7.

Thank you.

Kang

[Biliana Ficheva]

Hello,

Thank you for Contacting us.

Can you check whether the following forum thread addresses the issue on your side?
 http://www.telerik.com/community/forums/aspnet-ajax/vs-extensions/telerik-visual-studio-extensions-common-crash.aspx.

All the best,
Biliana Ficheva
the Telerik team

[Jeff]

Yeah, I think that post explains things.

I noticed on my Windows 7 machine that I still had KendoUI for MVC installed.  When I removed it VS stopped crashing.

So, you guys better get cracking and get a KendoUI release that's compatible with the Q3 components :)

--Jeff Lill

[Lasse]

I got the same crash. But this solution worked for me and I can now work with my old projects again.
Thanks

[Aylin]

Hi,

I am glad that the provided solution worked for you.

Do not hesitate to contact us if any questions arise.

Kind regards,
VSXTeam Aylin
the Telerik team