title: Finding the crash location inside NPAPI plugin in Chrome
body: <p>I've got an NPAPI plugin that works successfully on Chrome, Firefox, etc., except for one user, where it crashes in Chrome, but not in Firefox. I've installed Visual Studio on that user's machine, have downloaded the source files for my plugin, and am trying to debug the crash. I can attach to the appropriate chrome.exe process (thank you <code>--plugin-startup-dialog</code>), can set breakpoints, and can walk through my code. But there are several hundred thousand lines of code to debug, code that gets called multiple time a second, and I haven't found the right breakpoint yet. </p>
  
  <p>Normally, of course, when a process VS is debugging crashes, VS will report the crash, and give you the chance to look at the call stack. But with Chrome, the crash apparently never gets reported to VS, as the process just exits silently.</p>
  
  <p><a href="http://pushingtheweb.com/2010/06/debugging-npapi-plugins-in-visual-studio/" rel="nofollow">I'm told</a> that you can disable the equivalent behavior in Firefox, so that VS can handle the error, but I'm not sure how to do this in Chrome. Any ideas about how to get the crash reported to Visual Studio?</p>