Dump is causing linqpad to freeze

actnhn

Hi,

In latest beta LINQPad is freezing every time Dump is called on a table or object. It's very reproducible and very annoying.

actnhn

Calling Domain.GetComputerDomain().Name.Dump(); also causes LINQPad to freeze. I am running as C# program.

actnhn

more info, it's not just beta version. Even current release is doing the same. I am wondering if it has something to do with windows 10 Build 14295?

sgmoore

I've just tried using LinqPad v5.06.01 on a vm running build 14295 and it works fine.

actnhn

Not sure what's going on with my machine, anytime I call Dump(), LINQPad freezes.

JoeAlbahari

Can you reproduce this on any other machine?

actnhn

No, I cannot. Any idea how can I debug the issue?

actnhn

actnhn

Here is a screenshot of threads in Visual Studio

https://onedrive.live.com/redir?resid=A0E4337BA8E3A14!515434&authkey=!AJceZLElNq_ONaU&v=3&ithint=photo,png

JoeAlbahari

Looks like your Internet Explorer installation is hosed. It's hanging when accessing the Document property of the WebBrowser control.

dmarsh

I wanted to share the same stack trace analysis:



I don't think there's anything "corrupted" about @actnhn's installation, he's just on Windows10 Fast Ring, like me. This actually started about three Fast Ring builds ago. My thinking is that the IE WebBrowser control has maybe changed how it propagates this event in a way that maybe reveals some kind of bug in LINQPad's handling of the event and accessing of the document. Either that or Microsoft has done something in MSHTML that has introduced a bug into the Web Browser control and then I guess you should report that to them if that's ultimately your analysis of this problem.

JoeAlbahari

Thanks for the stack traces. Can you both try running the following query:

http://share.linqpad.net/vx89us.linq

and let me know the result.

Thanks

JoeAlbahari

Can you also please verify:

(a) whether the problem can be reproduced with a simple "Hello world".Dump(), and if not, whether Thread.Sleep(500); "Hello world".Dump() reproduces it

(b) if 'Auto Scroll Results to End' on the Query menu is enabled, whether disabling it makes any difference.

Thanks

actnhn

formatting the darn PC fixed the issue. It was getting impossible to live without LINQPad.

actnhn

FYI, Still on Windows 10 build 14316

dmarsh

Ok, good news! this appears to be working again in the latest Fast Ring build (14328).