What's the best way to debug this, knowing that the browser won't
always be in this state and this may be difficult if not impossible to
repro? Note this is a dev channel release.
Thanks,
James
I usually tell people to kill -SEGV the stuck process, then grab the
crash dump id and look at the stack from there.
(But now that I've written that, I'm not certain that actually works.)
You also might be able to attach with gdb and use the
(google-internal) symbols found on wiki/Main/LinuxDebugging.