Friday, May 22, 2015

Find a production bug that causes 100% CPU load

This actually happened in my previous job, but I hadn't shared it. We had a piece of software that caused the production server to run at 100% for a couple of minutes, before going down.

So we tried to analyze it using windbg first, using this excellent how-to:

But ... that didn't work. Because there was a mismatch between windbg or sos plugin on my machine and the .net version on the server or something. And of course - I was not able to touch the production server to do it on the machine itself.

Nevertheless, this is a great post. Check it out:

No comments:

Post a Comment