Thanks for sharing this issue. The code shown above is an old workaround we implemented to correct VS process memory management issues in older operating systems. I suspect the problem here may actually be indirect - although we're on the stack trace for this one, it's possible there is already heap corruption in place or there may be a plugin clash involved.
Can you confirm if this problem is still present for you? Or can be reproduced?
Visual Studio 2019 has been randomly crashing, since GA (The only third party plugins installed are R# and NCrunch). The fix is normally to delete the .vs folder cache.
This was the first time I was able to catch a dump, and every crash since has had the same stacktrace.
- Still present? - likely, but I can't prove that. The problem is currently mitigated.
- Reproducible? - I can reproduce the crash after the first occurance (until I delete the .vs folder cache), VS likes to crash silently and restart (so it loops until I kill VS with Taskmgr). I can't reproduce the first crash though.
What kind of sucks is that I can't live without NCrunch or R# :D - my productivity will definitely drop to test if either one causes the problem. If you don't think NCrunch is at fault, then I'll likely have to live with it. R# and VS is unlikely to provide any help with NCrunch in the stacktrace.
Silvenga wrote:
What kind of sucks is that I can't live without NCrunch or R# :D - my productivity will definitely drop to test if either one causes the problem. If you don't think NCrunch is at fault, then I'll likely have to live with it. R# and VS is unlikely to provide any help with NCrunch in the stacktrace.
Thanks for the extra detail. I can understand that there isn't really anything else you can do here. We've created a task on our side to pull this code out, as it's unlikely people are still using the environments it was intended to fix up. Probably it's creating more problems than it solves now.