Comment 21 for bug 240930

What's the behavior of this problem on a 32-bit system? Does flash consume overly high cpu usage by itself? Does it (and the browser) crash?

My guess is that npviewer.bin is getting into a crazy 100% cpu loop after the flash plugin crashes (there are lots of reports of that). In which case, nspluginwrapper should be responding better to this situation, likely by simply shutting down.

Is there a good way to get debugging information from nspluginwrapper, so we can get some idea what it's doing?