Closed Bug 1454311 Opened 7 years ago Closed 7 years ago

Crash in libxul.so@0xdbd391 | libxul.so@0xfc5d29 | libxul.so@0x3785b2d | libxul.so@0xa62148 | libxul.so@0x8effeb | libxul.so@0x475cd83 | libxul.so@0xa54ffc | libxul.so@0xa554ee | libxul.so@0x475cd83 | libxul.so@0xa585bf | libxul.so@0x475cd83 | libxul.s...

Categories

(Core :: XUL, defect)

Product:
Core
Component:
XUL
Version:
60 Branch
Platform:
Unspecified
Linux
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: matrix.org, Unassigned)

Details

Crash Data

This bug was filed from the Socorro interface and is report bp-2ec3e30a-f223-4541-a2e6-b4b690180416. ============================================================= Top 10 frames of crashing thread: 0 libxul.so libxul.so@0xdbd391 1 libxul.so libxul.so@0xfc5d29 2 libxul.so libxul.so@0x3785b2d 3 libxul.so libxul.so@0xa62148 4 libxul.so libxul.so@0x8effeb 5 libxul.so libxul.so@0x475cd83 6 libxul.so libxul.so@0xa54ffc 7 libxul.so libxul.so@0xa554ee 8 libxul.so libxul.so@0x475cd83 9 libxul.so libxul.so@0xa585bf ============================================================= This crash happens "randomly" often after clicking a link. However after restart clicking the same link usually won't cause a crash. It is not uncommon for FF to run for 10s of minutes between crashes, although they are often more common.
Component: XUL → General
Emma: why do you believe these are similar? This appears to be an assertion (see the MOZ_CRASH_REASON in Metadata - mWorkerThread == current virtual thread assert), and that doesn't appear in the other. Also, this appears to be a non-mozilla build, which we can't symbolicate, which is why all the libxul.so stuff; there's no reason to think that's related to the raspberry pi libxul crashes (again, we don't do that build, so we don't have symbols for it)
Flags: needinfo?(ehumphries)
Yes, this is my misreading those and forgetting that this was a packager build.
Flags: needinfo?(ehumphries)
Which distro is this, Kevin? You may need to follow up with the packagers.
Flags: needinfo?(kevincox)
This was on Arch Linux. I tried rebuilding with less optimization and enabling debug symbols but it didn't appear to show up in the uploaded crash dumps. The final workaround was doing a profile refresh which prevented the bug from triggering.
Flags: needinfo?(kevincox)
Component: General → XUL
Triage: sadly this is not actionable & with no stack trace or function names to dedup. Given that a profile refresh fix this I am going to close this as WFM. Feel free to reopen if there is more related information (e.g. if you'd saved the profile and being able to produce the same crash with stack).
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
Are there instructions for complaining with debug symbols? I couldn't find them and some promising sounding flags didn't do the truck.
You need to log in before you can comment on or make changes to this bug.