This report also contains technical information about the state of the application when it crashed.
Means nothing to me but at a quick glance I’d say it is something to do wiht one of my (few) extensions. - Problem is - which one?
Any way to tell from this crash report?
The only recognisable thing I can see there is the dictionary - but surely that wouldn’t cause a crash?
Fair enough. I didn’t realise I needed a body of proof to relate my experience. In any case, I have found Firefox to be unstable with the most recent updates, and it does crash daily for me. I haven’t had time to investigate. Incidentally I’ve been using Firefox on SLED since 2005 and it is very stable.
> Fair enough. I didn’t realise I needed a body of proof to relate my
It’s not a question of proof, it’s a question of evidence. Without
evidence, there’s no chance at all that the problem will get fixed,
because nobody else knows how to reproduce it or even what exactly ‘it’ is.
Well it’s a vanilla install of openSUSE 12.1 with only muzlocker font smoothing repo added and 1-click restricted formats multimedia install. No extra add ins or anything to Firefox. It just bombs out when a link opens another Firefox window. Sometimes, not all the time. And by submitting the reports to Mozilla a presume it will get fixed upstream eventually.
Am 30.03.2012 06:56, schrieb farcusnz:
> is anybody else finding Firefox 11 to be a little unstable?
> I am running it on 12.1 x86-64 KDE 4.7
> It just seems to totally crash from time to time.
> When crashes I get a window asking if I want to restart or quit
> If I click restart - it does not restart.
> If it is just me then I probably need to do a little more
Guys, Firefox has this nice feature to send crash reports. Please use
that, find your crash ids under about:crashes and send it along with
your reports. The cut’n’paste from above tells nothing at all.
I invested a lot of time to make crash reports from openSUSE packages
useful in the upstream crash collector to make your and my life easier.
Am 31.03.2012 14:36, schrieb farcusnz:
> isn’t the information in about:crashes the information that has already
> been submitted to mozilla via the crash handler?
It is. But just in case these crashes are openSUSE specific noone will
probably notice them unless it’s a top crasher.
If people want to be sure that the crash is being looked at some
additional trigger is needed. That is for example filing a bug at bugzilla.mozilla.org or bugzilla.novell.com and refer to the crash report.
Maybe unrelated to your issue, but I’m noticing problems with Firefox in recent days and struggling to get to the bottom of it all. Could be a wider Mozilla-related issue because neither Thunderbird nor a first-time install of SeaMonkey are behaving normally for me either. All very sluggish, and Firefox in particular seems to have problems with Twitter and the loading of a large percentage of other sites. I’m in the middle of trying various things but can’t figure it out yet.
On a laptop with a freshly installed 12.1 and KDE all was well until a few days ago, maybe it started with Firefox 11 - will roll back to 10 and see what that does. Opera on same machine seemingly not experiencing such issues, and another slower system running oS 12.1 and XFCE behind the same router is now faster for browsing and doesn’t have these problems. I tried changing the connection in Mozilla apps to ‘No proxy’ instead of ‘Auto’ and that seemed to make Thunderbird connect to the mail server much quicker, but it shouldn’t make any difference as I have no proxy set up anyway.