Bug 1594692 - [RHEL6/s390x] segfault in allocateFromFreeList
Summary: [RHEL6/s390x] segfault in allocateFromFreeList
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: firefox
Version: 6.10
Hardware: s390x
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Martin Stransky
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 1556892
TreeView+ depends on / blocked
 
Reported: 2018-06-25 08:29 UTC by Tomas Pelka
Modified: 2021-09-09 14:43 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Known Issue
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-03 12:29:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
ff bt (71.69 KB, text/plain)
2018-06-25 08:29 UTC, Tomas Pelka 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1472970 0 None None None 2019-07-03 13:42:03 UTC

Description Tomas Pelka 2018-06-25 08:29:14 UTC 
Created attachment 1454276 [details]
ff bt

Description of problem:
Program received signal SIGSEGV, Segmentation fault.
allocateFromFreeList (this=0x3ffffdb5dc0, src=0x3ffec314158)
    at /usr/src/debug/firefox-60.1.0/js/src/gc/ArenaList-inl.h:344
344	    return freeList(thingKind)->allocate(thingSize);

Version-Release number of selected component (if applicable):
firefox-60.1.0-4.el6

How reproducible:
100%

Steps to Reproduce:
1. startup firefox
2.
3.

Actual results:
startup segfault 

Expected results:
no segfault, ff should start 

Additional info:
might be variation of bz1594664
Comment 2 Martin Stransky 2018-07-03 06:32:53 UTC 
This is a crash at JS engine on s390x and we don't have a fix for that.
Comment 3 Martin Stransky 2018-07-03 11:35:35 UTC 
Upstream bug https://bugzilla.mozilla.org/show_bug.cgi?id=1472970
Comment 4 kinerak 2018-09-13 01:10:41 UTC 
i'm hitting the same issue but with different application. is there any update on the fix in allocateFromFreeList()?
Comment 5 Martin Stransky 2018-09-13 07:36:05 UTC 
Sorry, no update yet.
Comment 6 kinerak 2018-09-14 00:05:06 UTC 
np. it is an known issue? any workaround can be used?
Comment 7 Martin Stransky 2018-09-14 06:21:26 UTC 
(In reply to kinerak from comment #6)
> np. it is an known issue? any workaround can be used?

Yes, it's a known issue and there's no workaround for it.
Note You need to log in before you can comment on or make changes to this bug.