Closed Bug 694950 Opened 10 years ago Closed 8 years ago
.0a1 Crash Report [@ libxul .so@0x10db8da ]
User Agent: Mozilla/5.0 (Ubuntu; X11; Linux i686; rv:10.0a1) Gecko/20111015 Firefox/10.0a1 Build ID: 20111015071525 Steps to reproduce: I restarted Firefox after installing ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-trunk/firefox-10.0a1.en-US.langpack.xpi (might be unrelated), and Firefox crashed. Actual results: Each time I load my session, it crashes. It works correctly when I open a new tab alongside about:sessionrestore, so this is likely a problem with one of my tabs.
Crash Signature: libxul.so@0x10db8da
The stack trace is without symbols. Do you use a build from Mozilla.org ? Kairo: Are there known problem with the symbols for linux ?
Sorry Kairo..... Yann: The crash reporter can only work if the debug symbols that are generated during building Firefox are uploaded to the crash server. You have to use a Mozilla.org build if you want to generate a useful stack trace with the crash reporter. Can you try a Mozilla.org build ( ftp://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ ), extract it for example in /tmp and run it from there ? The crash ID from this build should be useable.
OK, so, 1) this is from something called "Firefox-Trunk" which is a name used by ubuntu builds and something Mozilla doesn't really support or care about. 2) Not having any reasonable crash info due to missing symbols is also ubuntu's fault. Still, Chris, who is the ubuntu maintainer for Firefox packages, might want to know about this.
Note, we do generate and submit symbols for these. This isn't the first time it hasn't worked properly though. These are basically just nightly builds but renamed to make them co-installable with other builds, so crashes generally might be interesting
(In reply to Chris Coulson from comment #5) > These are basically just nightly builds > but renamed to make them co-installable with other builds, so crashes > generally might be interesting That might be true in theory, but the Mozilla crash investigation team will not look at anything that does not state "Firefox" as its product. We don't recognize "Firefox-Trunk" and our tools also don't and won't.
(In reply to Chris Coulson from comment #5) > Note, we do generate and submit symbols for these. This isn't the first time > it hasn't worked properly though. Sorry, should have addressed that in some way as well. Ted, any idea what's going wrong for them there?
(In reply to Robert Kaiser (:firstname.lastname@example.org) from comment #6) > (In reply to Chris Coulson from comment #5) > > These are basically just nightly builds > > but renamed to make them co-installable with other builds, so crashes > > generally might be interesting > > That might be true in theory, but the Mozilla crash investigation team will > not look at anything that does not state "Firefox" as its product. We don't > recognize "Firefox-Trunk" and our tools also don't and won't. Oh, sorry, I didn't realize that. I've switched this off for now for our nightly builds
The symbols for this particular build don't appear to be on the symbol server: [tmielczarek@dm-symbolpush01 symbols_ubuntu]$ pwd /mnt/netapp/breakpad/symbols_ubuntu [tmielczarek@dm-symbolpush01 symbols_ubuntu]$ ls libxul.so/3CB3E9DA438844F4E92F39B91CB5B4700 ls: libxul.so/3CB3E9DA438844F4E92F39B91CB5B4700: No such file or directory
There are nu crashes with this signature in Socorro: https://crash-stats.mozilla.com/query/?product=Firefox&version=ALL%3AALL&range_value=4&range_unit=weeks&date=11%2F07%2F2013+10%3A00%3A00&query_search=signature&query_type=contains&query=libxul.so%400x10db8da&reason=&release_channels=&build_id=&process_type=any&hang_type=any Can you still reproduce this issue with current Firefox builds?
I guess not. :)
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.