WinDbg is also not the only program out there to analyze minidumps – for example, whocrashed. On Windows, the default tool to use is WinDbg, which you might already have on your computer if you are a developer it is available as part of the Windows 10 SDK.
However, this is not true minidump is a standardized dump format, actually created by Microsoft for Windows specifically, and there is more than just one tool to analyze them. The page from Chromium on decoding crash dumps makes it kind of sound like this is impossible to do on Windows and requires very specialized Unix tools. Now how do we read these files? If you are a newbie to this part of software, like I am, you might be a little lost. Breakpad is what used to be used, but is getting replaced by Crashpad, which is now used by default on Windows and Mac.) (EDIT: This helpful page from Chromium on Crash Reports cleared this up more. They are saved as files with the “DMP” extension, which would indicate “Dump files”, but they are actually “minidump” files, which I confirmed by checking the magic bytes (first 6 bytes read as “MDMP“§”) and then referring to the readme for Crashdump and Breakpad, which are the Chromium tools that actually are responsible for saving and generating the files. I found them in “C:\Users\\AppData\Local\Google\Chrome\User Data\Crashpad\reports”, but your location may differ. However, I noticed that even with that setting off, and and chrome://crashes/ showing “Crash reporting is disabled.”, the actual crash dump files were being generated and saved anyways. Using Chrome’s Crash Reports:Ī quick Google search pulled up this SuperUser post, that says you need to enable the sharing of usage stats and crash reports with Google Corporate in order to use them, which I did not want to do.
So next I looked to using Chrome’s crash reports.
Trying to use Chrome’s dev tools panel wasn’t much help as, well… it crashed along with the browser whenever this happened. Understandably, I got frustrated, but I never like being one of those people that just complains without knowing why, so I wanted to see if I could dig a little deeper. I’m not talking about the “this tab has crashed” message, I’m talking acts-like-a-kernel-panic, no error shown, every single tab and entire app window exists type crash. After recently updating Chrome, I ran into certain sites hard-crashing the entire application on certain actions.
0 kommentar(er)
