Unfortunately, this is the same stack trace that you reported previously when calling Dump caused a hang.
I've uploaded a new beta that avoids touching the web browser upon startup, so it should allow you to start LINQPad, but I suspect it will hang when you call Dump.
If you remove the while loop where it is stuck, does it still correctly display Test and Test2? And what ReadyState does it report (instead of Complete?)
Even after removing the while loop the query is stuck. When I tried to put a breakpoint to inspect the ReadyState a exception occurred. I reported the error.
Comments
> System.Windows.Forms.dll!System.Windows.Forms.WebBrowser.Document.get() Unknown
System.Windows.Forms.dll!System.Windows.Forms.WebBrowser.WebBrowserEvent.DocumentComplete(object pDisp, ref object urlObject) Unknown
[Native to Managed Transition]
[Managed to Native Transition]
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows.Forms.dll!System.Windows.Forms.WebBrowser.Document.get() Unknown
System.Windows.Forms.dll!System.Windows.Forms.WebBrowser.WebBrowserEvent.DocumentComplete(object pDisp, ref object urlObject) Unknown
[Native to Managed Transition]
[Managed to Native Transition]
[Native to Managed Transition]
[Managed to Native Transition]
System.Windows.Forms.dll!System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(System.IntPtr dwComponentID, int reason, int pvLoopData) Unknown
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(int reason, System.Windows.Forms.ApplicationContext context) Unknown
System.Windows.Forms.dll!System.Windows.Forms.Application.ThreadContext.RunMessageLoop(int reason, System.Windows.Forms.ApplicationContext context) Unknown
LINQPad.exe!LINQPad.Program.Run(string queryToLoad, bool runQuery, string activationCode, bool activateAll, bool deactivate, bool noForward, bool noUpdate, string caller) Unknown
LINQPad.exe!LINQPad.Program.Go(string[] args) Unknown
LINQPad.exe!LINQPad.Program.Start(string[] args) Unknown
LINQPad.exe!LINQPad.ProgramStarter.Run(string[] args) Unknown
LINQPad.exe!LINQPad.Loader.Main(string[] args) Unknown
[Managed to Native Transition]
> System.Core.dll!System.IO.Pipes.NamedPipeServerStream.WaitForConnection() Unknown
LINQPad.exe!LINQPad.Program.Listen() Unknown
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) Unknown
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) Unknown
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Unknown
mscorlib.dll!System.Threading.ThreadHelper.ThreadStart() Unknown
I've uploaded a new beta that avoids touching the web browser upon startup, so it should allow you to start LINQPad, but I suspect it will hang when you call Dump.
Can you try running the following query, either on the new beta or release version that works for you:
http://share.linqpad.net/lbmgqx.linq
and let me know the result.
Thanks
while (browser.ReadyState != WebBrowserReadyState.Complete)
Now I am using latest release.
Yes, you're right, calling Dump causes it to freeze.
Is there a way to add some timeout to web browser ready detection?
http://www.awesomium.com/
It's pretty neat and we use it on our product as well.
IE does work fine on the machine.