Closed
Bug 1342894
Opened 7 years ago
Closed 7 years ago
Crash in libc-2.23.so@0x9889d
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: z.vanya, Unassigned)
References
Details
Crash Data
This bug was filed from the Socorro interface and is report bp-d5974174-a6fc-46d5-b913-b3b3e2170227. ============================================================= I've been having this problem with ALT's build of firefox: firefox-esr-45.7.0-alt0.M70P.1 and 51.0.1-alt2 . Now also with vanilla firefox 51.0.1 . The --sync and --safe-mode don't make it go away. If I open this URL under a fresh user, the crash is not reproduced. So, it must be some interactions in my profile... But I'm reproducing it 100% after I restore the session and switch to the tab which is causing the problem. I'm going to continue testing this with future versions of firefox... Results: the crash is reproducible in firefox 53 (nightly).
The crash in vanilla firefox 51: https://crash-stats.mozilla.com/report/index/bp-d5974174-a6fc-46d5-b913-b3b3e2170227 The same crashes in firefox 53 (nightly): https://crash-stats.mozilla.com/report/index/bp-a436f4e3-8596-43f8-b882-3b3762170227 https://crash-stats.mozilla.com/report/index/bp-a9a3af42-4ccc-4b5c-b16b-8451d2170227 https://crash-stats.mozilla.com/report/index/bp-f7fd4ea6-5085-46e1-9a4d-13eac2170227
Comment 3•7 years ago
|
||
The reason is probably not a bug in firefox, but a buggy libfreetype-infinality-2.4.11-alt6.M70P.2 , which was tracked down by me thanks to the backtrace. I've done tests with other newer versions of this package (and without it, with using standard libfreetype), and the crash doesn't reproduce itself in those cases -- https://bugzilla.altlinux.org/show_bug.cgi?id=33181 .
The reason is probably not a bug in firefox, but a buggy libfreetype-infinality-2.4.11-alt6.M70P.2 -- https://bugzilla.mozilla.org/show_bug.cgi?id=1342894#c3 .
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•