Bug 1757679 - [OOM] firefox killed by SIGSEGV
Summary: [OOM] firefox killed by SIGSEGV
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 31
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
 
Reported: 2019-10-02 06:55 UTC by sumantro
Modified: 2019-11-05 13:11 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-11-05 13:11:44 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
ABRT backtrace (238.66 KB, text/plain)
2019-10-02 06:55 UTC, sumantro 		no flags Details
View All

Description sumantro 2019-10-02 06:55:38 UTC 
Created attachment 1621741 [details]
ABRT backtrace

Description of problem:
Crash function : WasmTrapHandler(int, siginfo_t*, void*) [clone .lto_priv.0]

Version-Release number of selected component (if applicable):
firefox-69.0.1-3.fc31

How reproducible:
Once every 6 hrs

Steps to Reproduce:
1. Open Firefox in wayland
2. keep using it and it will freeze and tabs cant be closed anymore
3.

Actual results:


Expected results:


Additional info:
Comment 1 Martin Stransky 2019-10-02 07:24:34 UTC 
mozalloc_handle_oom() - it's out of memory crash. Can you reproduce it?
Comment 2 sumantro 2019-10-09 08:26:08 UTC 
Yes I can reproduce it almost evry other day.
Comment 3 dr.nukular 2019-10-14 14:27:25 UTC 
I'm getting the exact same error message after firefox crashes, which happens each time I clear the browser history using the dedicated button, where I can choose to delete the history from 5 minutes, 2 or 24 hours ago. This is reproducible almost each time (9/10 times) using the same version of Fedora and Firefox as specified above.
Comment 4 Martin Stransky 2019-11-05 13:11:44 UTC 
Thanks, this should be fixed in Firefox 71 - https://bugzilla.mozilla.org/show_bug.cgi?id=1588448
Note You need to log in before you can comment on or make changes to this bug.