Closed Bug 1115144 Opened 10 years ago Closed 9 years ago

Intermittent test_pluginstream_err.html | application crashed [@ PR_DestroyCondVar]

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: RyanVM, Unassigned)

References

Details

(Keywords: crash, intermittent-failure) 

11:25:12 INFO - 410 INFO TEST-PASS | dom/plugins/test/mochitest/test_pluginstream_err.html | test frame has unexpected content
11:25:12 INFO - 411 INFO TEST-FAIL | dom/plugins/test/mochitest/test_pluginstream_err.html | The author of the test has indicated that flaky timeouts are expected. Reason: untriaged
11:25:12 INFO - 412 INFO TEST-PASS | dom/plugins/test/mochitest/test_pluginstream_err.html | plugin reported an error
11:25:12 INFO - 413 INFO TEST-FAIL | dom/plugins/test/mochitest/test_pluginstream_err.html | The author of the test has indicated that flaky timeouts are expected. Reason: untriaged
11:25:12 INFO - 414 INFO MEMORY STAT vsize after test: 529874944
11:25:12 INFO - 415 INFO MEMORY STAT residentFast after test: 79785984
11:25:12 INFO - 416 INFO MEMORY STAT heapAllocated after test: 21917656
11:25:12 INFO - 417 ERROR TEST-UNEXPECTED-FAIL | dom/plugins/test/mochitest/test_pluginstream_err.html | application terminated with exit code 11
11:25:12 INFO - runtests.py | Application ran for: 0:02:34.793703
11:25:12 INFO - zombiecheck | Reading PID log: /tmp/tmpgKfJAApidlog
11:25:12 INFO - ==> process 2229 launched child process 2269
11:25:12 INFO - ==> process 2229 launched child process 2555
11:25:12 INFO - ==> process 2229 launched child process 2563
11:25:12 INFO - ==> process 2229 launched child process 2571
11:25:12 INFO - ==> process 2229 launched child process 2576
11:25:12 INFO - ==> process 2229 launched child process 2581
11:25:12 INFO - zombiecheck | Checking for orphan process with PID: 2269
11:25:12 INFO - zombiecheck | Checking for orphan process with PID: 2555
11:25:12 INFO - zombiecheck | Checking for orphan process with PID: 2563
11:25:12 INFO - zombiecheck | Checking for orphan process with PID: 2571
11:25:12 INFO - zombiecheck | Checking for orphan process with PID: 2576
11:25:12 INFO - zombiecheck | Checking for orphan process with PID: 2581
11:25:12 INFO - mozcrash Downloading symbols from: https://ftp-ssl.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-central-linux/1419358652/firefox-37.0a1.en-US.linux-i686.crashreporter-symbols.zip
11:25:39 INFO - mozcrash Saved minidump as /builds/slave/test/build/blobber_upload_dir/1d65937d-cae3-6755-559cdbba-2623e070.dmp
11:25:39 INFO - mozcrash Saved app info as /builds/slave/test/build/blobber_upload_dir/1d65937d-cae3-6755-559cdbba-2623e070.extra
11:25:39 WARNING - PROCESS-CRASH | dom/plugins/test/mochitest/test_pluginstream_err.html | application crashed [@ PR_DestroyCondVar]
11:25:39 INFO - Crash dump filename: /tmp/tmpJXT2l6.mozrunner/minidumps/1d65937d-cae3-6755-559cdbba-2623e070.dmp
11:25:39 INFO - Operating system: Linux
11:25:39 INFO - 0.0.0 Linux 3.2.0-23-generic-pae #36-Ubuntu SMP Tue Apr 10 22:19:09 UTC 2012 i686
11:25:39 INFO - CPU: x86
11:25:39 INFO - GenuineIntel family 6 model 45 stepping 7
11:25:39 INFO - 1 CPU
11:25:39 INFO - Crash reason: SIGSEGV
11:25:39 INFO - Crash address: 0x34
11:25:39 INFO - Thread 0 (crashed)
11:25:39 INFO - 0 libnspr4.so!PR_DestroyCondVar [ptsynch.c:44344099d119 : 338 + 0x0]
11:25:39 INFO - eip = 0xb71e2d6a esp = 0xbf973350 ebp = 0xbf973368 ebx = 0xb71fd54c
11:25:39 INFO - esi = 0x00000000 edi = 0x00000000 eax = 0x965291e0 ecx = 0x000003e8
11:25:39 INFO - edx = 0x9eca4dc4 efl = 0x00210282
11:25:39 INFO - Found by: given as instruction pointer in context
11:25:39 INFO - 1 libxul.so!mozilla::Monitor::~Monitor() [CondVar.h:44344099d119 : 61 + 0xa]
11:25:39 INFO - eip = 0xb372aef4 esp = 0xbf973370 ebp = 0xbf973388 ebx = 0xb6edeb30
11:25:39 INFO - esi = 0x965291e0 edi = 0x00000000
11:25:39 INFO - Found by: call frame info
11:25:39 INFO - 2 libxul.so!mozilla::layers::CompositorParent::~CompositorParent() [CompositorParent.cpp:44344099d119 : 408 + 0xe]
11:25:39 INFO - eip = 0xb3c78f57 esp = 0xbf973390 ebp = 0xbf9733a8 ebx = 0xb6edeb30
11:25:39 INFO - esi = 0x96529000 edi = 0x00000000
11:25:39 INFO - Found by: call frame info
11:25:39 INFO - 3 libxul.so!mozilla::layers::CompositorParent::~CompositorParent() [CompositorParent.cpp:44344099d119 : 412 + 0x8]
11:25:39 INFO - eip = 0xb3c78fd0 esp = 0xbf9733b0 ebp = 0xbf9733c8 ebx = 0xb6edeb30
11:25:39 INFO - esi = 0x96529000 edi = 0x00000000
11:25:39 INFO - Found by: call frame info
11:25:39 INFO - 4 libxul.so!mozilla::layers::DeleteOnMainThreadTask<mozilla::layers::CompositorParent>::Run() [CompositorParent.h:44344099d119 : 130 + 0xc]
11:25:39 INFO - eip = 0xb3c4d309 esp = 0xbf9733d0 ebp = 0xbf9733e8 ebx = 0xb6edeb30
11:25:39 INFO - esi = 0xb7221550 edi = 0x00000000
11:25:39 INFO - Found by: call frame info
11:25:39 INFO - 5 libxul.so!nsThread::ProcessNextEvent(bool, bool*) [nsThread.cpp:44344099d119 : 855 + 0x5]
11:25:39 INFO - eip = 0xb372e960 esp = 0xbf9733f0 ebp = 0xbf973458 ebx = 0xb6edeb30
11:25:39 INFO - esi = 0xb7221550 edi = 0x00000000
11:25:39 INFO - Found by: call frame info
11:25:39 INFO - 6 libxul.so!NS_ProcessNextEvent(nsIThread*, bool) [nsThreadUtils.cpp:44344099d119 : 265 + 0xf]
11:25:39 INFO - eip = 0xb3743bb9 esp = 0xbf973460 ebp = 0xbf973498 ebx = 0xb6edeb30
11:25:39 INFO - esi = 0xb1004fa0 edi = 0xb721e8a0
11:25:39 INFO - Found by: call frame info
11:25:39 INFO - 7 libxul.so!mozilla::ipc::MessagePump::Run(base::MessagePump::Delegate*) [MessagePump.cpp:44344099d119 : 140 + 0xb]
11:25:39 INFO - eip = 0xb390fde0 esp = 0xbf9734a0 ebp = 0xbf9734e8 ebx = 0xb6edeb30
11:25:39 INFO - esi = 0xb1004fa0 edi = 0xb721e8a0
11:25:39 INFO - Found by: call frame info
See Also: → 1120898
Between this bug and the various See Alsos, this test is quickly becoming a crash-prone trainwreck.
Flags: needinfo?(milan)
See Also: → 1120879
It really cranked up today, didn't it. I couldn't reproduce this locally on a Dec 30th build, let me try it on a fresh one, if it reproduces there may be a patch that increased the frequency.
I think backed out the cause for the immediate spike. It waits to be seen if that's right, though.
https://bugzilla.mozilla.org/show_bug.cgi?id=567058#c27
Flags: needinfo?(milan)
Ryan - did the backout help?
Flags: needinfo?(ryanvm)
Yes
Flags: needinfo?(ryanvm)
Inactive; closing (see bug 1180138).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.