Open
Bug 1297598
Opened 8 years ago
Updated 8 years ago
assertion failure---failure to allocate object
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: democritus7, Unassigned)
Details
(Keywords: assertion)
User Agent: Mozilla/5.0 (X11; Linux i686; rv:42.0) Gecko/20100101 Firefox/42.0 SeaMonkey/2.39 Build ID: 20151103174417 Steps to reproduce: I started Seamonkey in a terminal window and was just doing routine browsing (Facebooking) Actual results: The browser crashed showing the crash/bug report panel and asked if I wanted a restart or not. The msg in the terminal window was: Assertion failure: [unhandlable oom] Failed to allocate object while tenuring., at /builds/slave/rel-c-rel-lnx-bld/build/mozilla/js/src/jscntxt.cpp:1221 Expected results: The browser should not have crashed. If there was an assertion failure, maybe it should have retried.
Reporter | ||
Comment 1•8 years ago
|
||
I am running Mageia 5 Linux with a X86 server kernel on a 64-bit system and 4 gb of main memory. I had the same problem with Seamonkey 2.40 so I reverted to 2.39 to see if the crashes would stop. But v. 2.39 has what appears to be the same problem. Will try some nightly testing, I guess.
Comment 2•8 years ago
|
||
@reporter: a) Please publish the crah ID, you can find it under URL <about:crahses> b) Is that crash reproducible for you or was that a single event?
Reporter | ||
Comment 3•8 years ago
|
||
Here are the most recent crashes. There have been several. Report ID Date Submitted bp-9a221b76-4ad0-45b4-86f0-a51062160824 08/23/2016 11:01 PM bp-bd326bb2-c9ed-445a-8231-1dd3d2160823 08/22/2016 09:13 PM It's not reproducible. My amateur guess is that the program tries to use memory before it's been properly allocated. As noted above, my pc has 4 gb of RAM, no idea how much is available at the time of the crashes.
Comment 4•8 years ago
|
||
Crash Reason: SIGSEGV
Reporter | ||
Comment 5•8 years ago
|
||
Would an upgrade of libsigsegv help to stop these crashes?
Reporter | ||
Comment 6•8 years ago
|
||
Mageia 5 uses libsigsegv 2.10 release 5.mga5.
Reporter | ||
Comment 7•8 years ago
|
||
I had quite a few crashes today using 2.40, and decided to revert to an earlier version that didn't have crashes often. 2.39 has them, so I switched to 2.38, prepared to go back to 2.33.1 if needed. This particular link crashes consistently with version 2.40, but it displays ok in 2.38: https://www.facebook.com/groups/salinaraw/?multi_permalinks=1141065105964057¬if_t=group_highlights¬if_id=1474591283352948 I haven't tried the nightlies after release 2.40, but that would be a next step in finding the changes resulting in the frequent assertion crashes.
Reporter | ||
Comment 8•8 years ago
|
||
The frequent sigsegv crashes I've been having in 2.39 and 2.40 are evidently caused by changes made after the 2.38 release. So far, 2.38 hasn't crashed for me today.
You need to log in
before you can comment on or make changes to this bug.
Description
•