The relief of closing VS.Net
time to read 2 min | 228 words

After issuing the “pskill devenv” command,  memory consumption went from 0.99Gb(!) to 345Mb. And it is not like I’m doing anything special, for crying out loud.

There are additional problems beyond the outrageous memory requirements, for some reason I have time sensitive debugging now, if I wait more than a minute before moving to the next line, I get this error:

The CLR has been unable to transition from COM context 0x196730 to COM context 0x1968a0 for 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment (STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.

Just to top that, here is what happened when I tried to use the famous Edit & Continue feature:

Editing or deleting an active statement which is being executed will prevent the debug session from continuing while Edit and Continue is enabled.

This actually makes sense, it says: “No, we will not let you work today.”

Where is the promised service pack? I want more than a hint, I was actual improvement!

Tweet Share Share 0 comments
Tags: