Closed Bug 1529213 Opened 6 years ago Closed 6 years ago

Crash in [@ libxul.so@0x3f6789e | libxul.so@0x10b3eb2 | libxul.so@0x66a783f | libxul.so@0x3f72104 | libc-2.24.so@0xf5ba5]

Categories

(Firefox :: Untriaged, defect)

60 Branch
Unspecified
Linux
defect
Not set
critical

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: foss, Unassigned)

Details

Crash Data

This bug is for crash report bp-0c51d64d-db17-437a-b6f2-a74060190220.

Top 10 frames of crashing thread:

0 libxul.so libxul.so@0x3f6789e 
1 libxul.so libxul.so@0x10b3eb2 
2 libxul.so libxul.so@0x66a783f 
3 libxul.so libxul.so@0x3f72104 
4 linux-gate.so linux-gate.so@0xbd8 
5 libc-2.24.so libc-2.24.so@0xf5ba5 
6 libxul.so libxul.so@0x3f725b6 
7 libxul.so libxul.so@0x3f3196f 
8 libxul.so libxul.so@0x3f5357a 
9 linux-gate.so linux-gate.so@0xbd8 

I'm on Debian GNU/Linux 9 and since the migration to Firefox ESR 60.5.1 I observe many crashes on website.

I consider this as an important bug because I've to switch to Chrome to use certain website like to manage my bank account.

I'm not an export in the crash area so let me know if I could provide more details.

Best regards,
Alex.

The crash report is useless because it's missing the debug symbols.
This is most likely because you use a debian generated build and the Mozilla crash server doesn't have the debug symbols for those builds.

Please use a Mozilla.org build from here https://www.mozilla.org/en-US/firefox/organizations/all/, extract it into /tmp/, close all Firefox windows from your Debian installation and run the Mozilla.org build from /tmp/.

A crash report from this build should be working.

edited by emceeaich to update recommended non ftp url for ESR downloads

Flags: needinfo?(alexarnaud)

Based on the lack of information from the reporter this bug will have the Status: Resolved as incomplete.
If you want to add more info that can help to understand this bug please reopen it.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
Flags: needinfo?(alexarnaud)
You need to log in before you can comment on or make changes to this bug.