Not really. I never tried reproducing the bug, and I don't remember exactly what I was working on at the moment. I just sent the backtrace because the error reporter asked me to. Sorry. Anyway, it was a one time thing, I continued working OK after restarting the browser.
However, I'm not really in the know with this: is it possible to run Firefox in debug mode all the time (without huge performance penalties)? And, more importantly, is it useful for the developers? I'm getting crashes often enough, and I'll be willing to make an effort _if_ it's useful. However, most of the things that bother me are not (I think) easily reproducible. Things like an involuntary drag/drop while some other tab is loading that freeze the browser. I get stops like this a couple times a week, but I was never able to find out the reason (i.e., to reproduce it). So, again, is a debug trace by itself (no steps to reproduce) useful? -- Bogdan -- Crash while spell-checking in Writely https://launchpad.net/bugs/59873 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
