Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Solved: It turns out that the affected machine had .NET 4.5 beta installed.
I have a C# application using .NET4 that deadlocks / hangs indefinitely in a call to
GC.AddMemoryPressure(12000000)
Since it is an in production app I can’t really share any code – however I would like to get some hints on what might make GC.AddMemoryPressure hang.
Thanks for your input.
It turns out that the affected machine had .NET 4.5 beta installed.
It seems that it wasn’t deadlocked since one core was fully saturated. The call to AddMemoryPressure seemed to end up in the function clr!CNameSpace::GcScanRoots that never returned.
Uninstalling 4.5 beta and installing .NET 4 seems to have fixed the problem.
If this was truly the problem then I sure hope MS fix it before release.