Closed
Bug 1371636
Opened 7 years ago
Closed 7 years ago
Visiting skype.com causes a segfault in FF 52.1.0 under CentOS 6.9
Categories
(Firefox :: Untriaged, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: bugzilla, Unassigned)
Details
(Keywords: crash)
User Agent: Mozilla/5.0 (X11; Linux i686; rv:49.0) Gecko/20100101 Firefox/49.0 SeaMonkey/2.46 Build ID: 20161213180120 Steps to reproduce: 1. Start firefox in safe mode (firefox --safe-mode) 2. go to skype.com Actual results: Firefox displays page momentarily, then dies with a segfault. Expected results: Firefox shouldn't have segfaulted.
Running in gdb, I see: Program received signal SIGSEGV, Segmentation fault. 0x026b2a27 in ?? () from /usr/lib/firefox/libxul.so
Any crash reports in the page about:crashes? If not, could you give a better stacktrace if possible: https://developer.mozilla.org/en-US/docs/Mozilla/How_to_get_a_stacktrace_for_a_bug_report
Unfortunately, I can't run the stock binary of firefox under CentOS 6.9, since it requires GTK3. I'm using the distribution-supplied binary. I've submitted a bug report on the CentOS bugzilla: https://bugs.centos.org/view.php?id=13412 Also, doing some more experimenting, I find that this only seems to affect the 32-bit CentOS firefox binaries, not the 64-bit. But, all of that seems moot now: CentOS released an updated binary on June 16 (firefox-52.2.0-1) that seems to have fixed the problem.
Comment 4•7 years ago
|
||
(In reply to bugzilla from comment #3) > But, all of that seems moot now: CentOS released an updated binary on June > 16 (firefox-52.2.0-1) that seems to have fixed the problem. Bugzilla that means this problem is fixed now? Thanks
Flags: needinfo?(bugzilla)
Comment 5•7 years ago
|
||
I will mark this as Resolved WFM based on comment 3. Please feel free to reopen or change it if you consider that this status is not the appropriate one.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(bugzilla)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•