OOM on Linux Talos Tp3?

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
10 years ago
6 years ago

People

(Reporter: roc, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
Linux
intermittent-failure
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1248646301.1248651167.30152.gz

Crash stack has:

Crash reason:  SIGABRT
Crash address: 0xffffe410

Thread 0 (crashed)
 0  0xffffe410
    eip = 0xffffe410   esp = 0xbfa715f4   ebp = 0xbfa71610   ebx = 0x0000190a
    esi = 0x0000190a   edi = 0xb66f7ff4   eax = 0x00000000   ecx = 0x0000190a
    edx = 0x00000006   efl = 0x00200206
 1  libc-2.6.1.so + 0x2c200
    eip = 0xb65de201   esp = 0xbfa71618   ebp = 0xbfa7173c
 2  libstdc++.so.6.0.9 + 0xbb6df
    eip = 0xb67c26e0   esp = 0xbfa71744   ebp = 0xbfa7177c
 3  libstdc++.so.6.0.9 + 0xb8f64
    eip = 0xb67bff65   esp = 0xbfa71784   ebp = 0xbfa7179c
 4  libstdc++.so.6.0.9 + 0xb8fa1
    eip = 0xb67bffa2   esp = 0xbfa717a4   ebp = 0xbfa717ac
 5  libstdc++.so.6.0.9 + 0xb90c9
    eip = 0xb67c00ca   esp = 0xbfa717b4   ebp = 0xbfa717cc
 6  libstdc++.so.6.0.9 + 0xb96fd
    eip = 0xb67c06fe   esp = 0xbfa717d4   ebp = 0xbfa717fc
 7  libxul.so!NS_NewEventListenerManager(nsIEventListenerManager**) [nsEventListenerManager.cpp:5e62c879c8d5 : 1405 + 0x9]
    eip = 0xb75f267c   esp = 0xbfa71804   ebp = 0xbfa7181c

Sure looks like an OOM abort. But this appears to be random since it only showed up on one box.
Whiteboard: [orange]
Blocks: 438871
We're not running Tp3 any more, have there been any cases of this on other test suites?
Mass marking whiteboard:[orange] bugs WFM (to clean up TBPL bug suggestions) that:
* Haven't changed in > 6months
* Whose whiteboard contains none of the strings: {disabled,marked,random,fuzzy,todo,fails,failing,annotated,leave open,time-bomb}
* Passed a (quick) manual inspection of bug summary/whiteboard to ensure they weren't a false positive.

I've also gone through and searched for cases where the whiteboard wasn't labelled correctly after test disabling, by using attachment description & basic comment searches. However if the test for which this bug was about has in fact been disabled/annotated/..., please accept my apologies & reopen/mark the whiteboard appropriately so this doesn't get re-closed in the future (and please ping me via IRC or email so I can try to tweak the saved searches to avoid more edge cases).

Sorry for the spam! Filter on: #FFA500
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → WORKSFORME
Keywords: intermittent-failure
Whiteboard: [orange]
You need to log in before you can comment on or make changes to this bug.