mochitest other fails with exit code 11 from crash in test_ctypes.xul at arena_run_dalloc

RESOLVED WORKSFORME

Status

()

defect
RESOLVED WORKSFORME
9 years ago
7 years ago

People

(Reporter: mossop, Unassigned)

Tracking

({intermittent-failure})

Trunk
x86
macOS
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [orange:time-bomb])

http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1273684650.1273685172.20579.gz&fulltext=1#err0
Linux mozilla-central opt test mochitest-other on 2010/05/12 10:17:30

Comment 1

9 years ago
This is a crash in jemalloc...

Comment 2

9 years ago
Over to jemalloc component for investigation.
Assignee: general → nobody
Component: JavaScript Engine → jemalloc
QA Contact: general → jemalloc
Here's the relevant snippet of the tinderbox log:

> 7282 INFO Running chrome://mochikit/content/chrome/toolkit/components/jsctypes-test/test_ctypes.xul...
> 7283 INFO TEST-PASS | chrome://mochikit/content/chrome/toolkit/components/jsctypes-test/test_ctypes.xul | Chrome test dir doesn't exist?!
> , writen 2612 bytes dump:
> HTTP/1.1 200 OK
> 
> content-type: text/html
[...]
> <li class="non-test invisible"><a href="/tests/">/tests/</a>
> </li>
> </ul>
> </body>
> </html>
> 
>  dropping our write flag and setting other socket read flag
> SSLTUNNEL(0x837a498): ssock(1)=0x83590b8 out_flags=1 :reading socket gracefully closed
> SSLTUNNEL(0x837a498): exiting root function for csock=0x8359460, ssock=0x83590b8
> TEST-UNEXPECTED-FAIL | automation.py | Exited with code 11 during test run
> INFO | automation.py | Application ran for: 0:01:29.640980
> INFO | automation.py | Reading PID log: /tmp/tmpQ8Z2BFpidlog
> ==> process 4184 launched child process 4245
> ==> process 4184 launched child process 4247
> ==> process 4184 launched child process 4249
> INFO | automation.py | Checking for orphan process with PID: 4245
> INFO | automation.py | Checking for orphan process with PID: 4247
> INFO | automation.py | Checking for orphan process with PID: 4249
> PROCESS-CRASH | automation.py | application crashed (minidump found)
[...]
> Operating system: Linux
>                   0.0.0 Linux 2.6.18-53.1.19.el5 #1 SMP Wed May 7 08:20:19 EDT 2008 i686
> CPU: x86
>      GenuineIntel family 6 model 15 stepping 8
>      1 CPU
> 
> Crash reason:  SIGSEGV
> Crash address: 0x4
> 
> Thread 18 (crashed)
>  0  firefox-bin!arena_run_dalloc [jemalloc.c:d9900a280f59 : 2724 + 0x1c]
>     eip = 0x0804ebb9   esp = 0xa49fb8b0   ebp = 0xa49fb948   ebx = 0x08054ae8
>     esi = 0xb7ea0000   edi = 0xa49fb91c   eax = 0xb7ea0060   ecx = 0xb7ea0060
>     edx = 0x00000000   efl = 0x00210286
>     Found by: given as instruction pointer in context
>  1  firefox-bin!free [jemalloc.c:d9900a280f59 : 4205 + 0x10]
>     eip = 0x0804f774   esp = 0xa49fb950   ebp = 0xa49fb978   ebx = 0x08054ae8
>     esi = 0x00000034   edi = 0xaa434000
>     Found by: call frame info
>  2  libmozjs.so!js::TraceRecorder::~TraceRecorder [jsutil.h:d9900a280f59 : 205 + 0x7]
>     eip = 0x002386d4   esp = 0xa49fb980   ebp = 0xa9183000   ebx = 0x002ba49c
>     esi = 0xa9183078   edi = 0xa9aa3080
>     Found by: call frame info
>  3  libmozjs.so!js::TraceRecorder::finishAbort [jstracer.cpp:d9900a280f59 : 2416 + 0x7]
>     eip = 0x0023a178   esp = 0xa49fb9b0   ebp = 0xa9183000   ebx = 0x002ba49c
>     esi = 0xa83b2a84   edi = 0xa9aa3080
>     Found by: call frame info
>  4  libmozjs.so!js::AbortRecordingImpl [jstracer.cpp:d9900a280f59 : 7235 + 0x21]
>     eip = 0x0023a2e1   esp = 0xa49fb9e0   ebp = 0xa9a93000   ebx = 0x002ba49c
>     esi = 0x00000000   edi = 0xa9183000
>     Found by: call frame info
>  5  libmozjs.so!js::TraceRecorder::monitorRecording [jstracer.cpp:d9900a280f59 : 7212 + 0x9]
>     eip = 0x002678b2   esp = 0xa49fb9f0   ebp = 0xa9a93000   ebx = 0x002ba49c
>     esi = 0x00000000   edi = 0xa9183000
>     Found by: call frame info
>  6  libmozjs.so!js_Interpret [jsops.cpp:d9900a280f59 : 78 + 0x11]
>     eip = 0x00183ada   esp = 0xa49fba20   ebp = 0xa49fbcc8   ebx = 0x002ba49c
>     esi = 0x00000000   edi = 0xa8279c00
>     Found by: call frame info
>  7  libmozjs.so!js_Invoke [jsinterp.cpp:d9900a280f59 : 831 + 0xe]
>     eip = 0x0018b427   esp = 0xa49fbcd0   ebp = 0xa49fbd2c   ebx = 0x002ba49c
>     esi = 0x00000000   edi = 0xa8279c74
>     Found by: call frame info
>  8  libxul.so!nsXPCWrappedJSClass::CallMethod [xpcwrappedjsclass.cpp:d9900a280f59 : 1696 + 0x14]
>     eip = 0x014487fc   esp = 0xa49fbda0   ebp = 0x00000008   ebx = 0x01b77cc8
>     esi = 0x00000001   edi = 0x00000001
>     Found by: call frame info
>  9  libxul.so!nsXPCWrappedJS::CallMethod [xpcwrappedjs.cpp:d9900a280f59 : 570 + 0x15]
>     eip = 0x014442c0   esp = 0xa49fc030   ebp = 0x00000001   ebx = 0x01b77cc8
>     esi = 0xaa8d6300   edi = 0xa49fc080
>     Found by: call frame info
> 10  libxul.so!PrepareAndDispatch [xptcstubs_gcc_x86_unix.cpp:d9900a280f59 : 95 + 0x17]
>     eip = 0x017a1f3c   esp = 0xa49fc060   ebp = 0x00000001   ebx = 0x01b77cc8
>     esi = 0x00000008   edi = 0xa49fc080
>     Found by: call frame info
> 11  libxul.so!nsDOMWorkerMessageHandler::DispatchEvent [nsDOMWorkerMessageHandler.cpp:d9900a280f59 : 329 + 0x8]
>     eip = 0x0125b2e4   esp = 0xa49fc120   ebp = 0x00000001   ebx = 0x01b77cc8
>     esi = 0x00000001   edi = 0xaa45b2e0
>     Found by: call frame info
> 12  libxul.so!nsDOMFireEventRunnable::Run [nsDOMWorker.cpp:d9900a280f59 : 939 + 0xb]
>     eip = 0x01257e00   esp = 0xa49fc220   ebp = 0xa80836a0   ebx = 0x01b77cc8
>     esi = 0x80004005   edi = 0xa9ca58c0
>     Found by: call frame info
> 13  libxul.so!nsDOMWorkerRunnable::Run [nsDOMThreadService.cpp:d9900a280f59 : 487 + 0x7]
>     eip = 0x01253226   esp = 0xa49fc250   ebp = 0xa80836a0   ebx = 0x01b77cc8
>     esi = 0xa80836ac   edi = 0xa8279c00
>     Found by: call frame info
> 14  libxul.so!nsThreadPool::Run [nsThreadPool.cpp:d9900a280f59 : 219 + 0x8]
>     eip = 0x01795d97   esp = 0xa49fc290   ebp = 0x00000000   ebx = 0x01b77cc8
>     esi = 0x00000000   edi = 0xa9589dc0
>     Found by: call frame info
> 15  libxul.so!nsThread::ProcessNextEvent [nsThread.cpp:d9900a280f59 : 527 + 0xa]
>     eip = 0x0179418b   esp = 0xa49fc2f0   ebp = 0x00000001   ebx = 0x01b77cc8
>     esi = 0x00000000   edi = 0xa885c9c0
>     Found by: call frame info
> 16  libxul.so!NS_ProcessNextEvent_P [nsThreadUtils.cpp : 250 + 0xf]
>     eip = 0x01763c29   esp = 0xa49fc330   ebp = 0xa49fc3b8   ebx = 0x01b77cc8
>     esi = 0xa49fc37c   edi = 0xa885c9c0
>     Found by: call frame info
> 17  libxul.so!nsThread::ThreadFunc [nsThread.cpp:d9900a280f59 : 253 + 0x9]
>     eip = 0x017948d6   esp = 0xa49fc360   ebp = 0xa49fc3b8   ebx = 0x01b77cc8
>     esi = 0xa49fc37c   edi = 0xa885c9c0
>     Found by: call frame info
> 18  libnspr4.so!_pt_root [ptthread.c:d9900a280f59 : 228 + 0x8]
>     eip = 0x008e4251   esp = 0xa49fc390   ebp = 0xa49fc3b8   ebx = 0x008ed54c
>     esi = 0xab596870   edi = 0x00000000
>     Found by: call frame info
> 19  libpthread-2.5.so + 0x52da
>     eip = 0x00c042db   esp = 0xa49fc3c0   ebp = 0xa49fc4a8   ebx = 0x00c12ff4
>     esi = 0x00000000   edi = 0xa49fcb90
>     Found by: call frame info
> 20  libc-2.5.so + 0xcd12d
>     eip = 0x0651a12e   esp = 0xa49fc4b0   ebp = 0x00000000
>     Found by: previous frame's frame pointer

Comment 4

9 years ago
Back to jseng, then.
Assignee: nobody → general
Component: jemalloc → JavaScript Engine
QA Contact: jemalloc → general
If it's a crash in the allocator, it's usually not a crash *from* the allocator, just from someone freeing twice, scribbling on memory, overflowing a buffer, etc.  :-)  Better to assume it's client code until proven otherwise through careful debugging, most optimally with valgrind (when it's not a Windows crash, at least).

Comment 6

9 years ago
Totally agree, hence the -> jseng :)
Just filed Bug 570254 on a similar-looking crash.
(that is: a crash with a different stack, but during the same test.)

Comment 10

9 years ago
Gonna close this out, since we haven't seen it since the initial report.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Whiteboard: [orange][orange:time-bomb] → [orange:time-bomb]
You need to log in before you can comment on or make changes to this bug.