Bug 40032 - Inspector 0.7 for Windows crashes on startup
Summary: Inspector 0.7 for Windows crashes on startup
Status: RESOLVED NORESPONSE
Alias: None
Product: Workbooks & Inspector
Classification: Xamarin
Component: Client: Windows ()
Version: 0.7.0
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: xamarininteractive
URL:
Depends on:
Blocks:
 
Reported: 2016-03-31 23:09 UTC by erikd
Modified: 2017-01-13 17:08 UTC (History)
6 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:


Attachments
Log file (3.22 KB, text/plain)
2016-03-31 23:09 UTC, erikd
Details


Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description erikd 2016-03-31 23:09:18 UTC
Created attachment 15576 [details]
Log file

1. Download and install inspector v0.7 on a Threshold 2 (Win10 10586) or Redstone 1 machine.
2. Start inspector
3. Select WPF
4. Press Create

Expected: Inspector starts.

Actual: Inspector crashes.

[Info][00:00:00] AppSession: Starting Xamarin Inspector client
[Critical][00:00:12.1029229] AppDomain: unhandled exception: System.InvalidCastException: Unable to cast COM object of type 'System.__ComObject' to interface type 'mshtml.IHTMLDOMNode'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{3050F5DA-98B5-11CF-BB82-00AA00BDCE0B}' failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)).
   at Xamarin.CrossBrowser.XcbWebView.get_Document()
   at Xamarin.Inspector.Windows.Client.AgentSessionWindow.<ReplWebView_LoadCompleted>d__49.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<>c.<ThrowAsync>b__6_0(Object state)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(Object obj)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at MS.Internal.CulturePreservingExecutionContext.Run(CulturePreservingExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
   at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
   at System.Windows.Application.RunDispatcher(Object ignore)
   at System.Windows.Application.RunInternal(Window window)
   at System.Windows.Application.Run(Window window)
   at Xamarin.Inspector.Windows.Client.App.Main(String[] args)
Comment 1 erikd 2016-03-31 23:15:41 UTC
I mentioned TH2 and RS1, because Inspector does launch successfully on one of my machines and I thought that machine was on TH1, but it looks like it was auto-updated to TH2 at some point.  I'm not sure why this repros on some machines and not others.
Comment 2 Sandy Armstrong [MSFT] 2016-03-31 23:18:57 UTC
Thanks for filing, we'll look into it! It could be that we need to bundle something that happens to exist on the machines where it works?
Comment 3 erikd 2016-03-31 23:28:20 UTC
I work on the Visual Studio team.  The repro machines have (a non public build of) Visual Studio "15" installed.  The non-repro machine has VS 2015 Update 1.  Maybe that's related.
Comment 4 Sandy Armstrong [MSFT] 2016-04-04 16:53:51 UTC
It's strange that the differentiating factor would be which version of VS is installed. Your reproduction steps are for creating a WPF workbook, which has no dependency on VS at all.

What .NET framework is installed on the machines where it works vs where it doesn't?

What version of IE (not Edge) is installed on the various machines?
Comment 5 erikd 2016-04-04 17:21:39 UTC
Broken:
IE: 11.1000.14312.0 (Update Versions: 11.0.24 (KB3093983))
.NET: 4.6.01055

Broken:
IE: 11.177.10586.0 (Update Versions: 11.0.29 (KB3139929))
.NET: 4.6.01055

Working:
IE: 11.17.10586.0 (Update Versions: 11.0.25 (KB3100773))
.NET: 4.6.01055
Comment 7 lawisnie 2016-07-07 12:59:29 UTC
Sandy,

I'm guessing a bit here, but are you guys embedding the COM interop types, or are you relying on PIA's to be installed?
http://stackoverflow.com/questions/31853699/mshtml-dll-on-windows-10
Comment 8 Arpit Jha 2016-10-12 12:36:42 UTC
I have checked this issue with Workbooks 0.10.0.627 and I am able to create Wpf app successfully.I am not able to reproduce this machine

On My machine VS 2013,2015 Enterprises installed.

@erikd, Could you please check this issue with latest and let me know if you are facing this issue again.

Screencast : http://www.screencast.com/t/1mNYhQ52D
Comment 9 erikd 2016-10-12 16:17:58 UTC
I just installed v0.10 this morning from https://download.xamarin.com/inspector/XamarinInteractive.msi.  Not sure what the build number is.

In any case, this still repros for me.  I captured a dump file if that's helpful.  It's 358MB though, so I can't attach it.
Comment 10 Arpit Jha 2016-10-14 11:14:26 UTC
@erikd, I have check this issue with build https://download.xamarin.com/inspector/XamarinInteractive.msi  and its work for me.

Can you please let me are you able to create and deploy WPF application in VS.
Is seems that your VS missed WPF Component installed
Comment 11 erikd 2016-10-14 15:50:01 UTC
Creating and launching WPF apps in VS works fine.
Comment 13 Sandy Armstrong [MSFT] 2016-10-17 15:41:10 UTC
@lawisnie we are not embedding mshtml interops. That could be the issue, I suppose. Thanks for the link.

I wish I had a system I could reproduce this on. I've tried on a normal home install of Windows 10 Anniversary Update, without any sort of dev environment installed, and the client works fine.

@erikd I can put together a one-off build for you that embeds interops if you'd be willing to test it.
Comment 14 erikd 2016-10-17 15:44:02 UTC
Sure, I'd be happy to.
Comment 16 Aaron Bockover [MSFT] 2017-01-13 17:08:07 UTC
Please reopen if this is still an issue with the latest release.