LINQPad becomes unresponsive on long running programs

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.



  • 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).
  • Nope, it was using like 200 mb of RAM overall
  • Is it reproducible?
  • I don't have another dataset handy to go through like that. I guess can try to reproduce with any long running query.
Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!