LINQPad becomes unresponsive on long running programs

bazzilic · January 2018

Wrote this code, connected to SQL Server 2017 on a different host. Left this overnight, when came back LINQPad was using one full core, interface extremely unresponsive. Took me good 10 minutes to finally click the stop script button.

JoeAlbahari · January 2018

Did you take note of whether it was using a lot of memory?

Including this.ObjectTrackingEnabled = false; should certainly reduce the memory consumption (and you don't need object tracking in this example).

bazzilic · January 2018

Nope, it was using like 200 mb of RAM overall

JoeAlbahari · January 2018

Is it reproducible?

bazzilic · January 2018

I don't have another dataset handy to go through like that. I guess can try to reproduce with any long running query.

LINQPad becomes unresponsive on long running programs

Comments