Closed Bug 1009992 Opened 7 years ago Closed 7 years ago

Intermittent test_bug448534.html | application crashed [@ CoreAudio + 0x1c7fe] after 2x ABORT: Aborting on channel error.: file MessageChannel.cpp, line 1531

Categories

(Core :: Audio/Video, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: KWierso, Unassigned)

References

Details

(Keywords: crash, intermittent-failure)

Crash Data

https://tbpl.mozilla.org/php/getParsedLog.php?id=39600355&tree=Fx-Team
Rev4 MacOSX Snow Leopard 10.6 fx-team opt test mochitest-1 on 2014-05-13 14:48:24 PDT for push 5b65a96a2b0c

slave: talos-r4-snow-085



15:03:32     INFO -  4568 INFO TEST-START | /tests/content/media/test/test_bug448534.html
15:03:35     INFO -  [956] ###!!! ABORT: Aborting on channel error.: file /builds/slave/fx-team-osx64-0000000000000000/build/ipc/glue/MessageChannel.cpp, line 1531
15:03:35     INFO -  [956] ###!!! ABORT: Aborting on channel error.: file /builds/slave/fx-team-osx64-0000000000000000/build/ipc/glue/MessageChannel.cpp, line 1531
15:03:38     INFO -  TEST-INFO | Main app process: killed by SIGHUP
15:03:38  WARNING -  TEST-UNEXPECTED-FAIL | /tests/content/media/test/test_bug448534.html | application terminated with exit code 1
15:03:38     INFO -  INFO | runtests.py | Application ran for: 0:10:36.452969
15:03:38     INFO -  INFO | zombiecheck | Reading PID log: /var/folders/u4/u4E93GeMEGyUL0TIM+991E+++-k/-Tmp-/tmp4AbeU_pidlog
15:03:38     INFO -  mozcrash INFO | Downloading symbols from: https://ftp-ssl.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-macosx64/1400013119/firefox-32.0a1.en-US.mac.crashreporter-symbols.zip
15:04:08  WARNING -  PROCESS-CRASH | /tests/content/media/test/test_bug448534.html | application crashed [@ CoreAudio + 0x1c7fe]
15:04:08     INFO -  Crash dump filename: /var/folders/u4/u4E93GeMEGyUL0TIM+991E+++-k/-Tmp-/tmpI_EozJ/minidumps/51323633-88F5-4F60-9B90-D8095006B564.dmp
15:04:08     INFO -  Operating system: Mac OS X
15:04:08     INFO -                    10.6.8 10K549
15:04:08     INFO -  CPU: amd64
15:04:08     INFO -       family 6 model 23 stepping 10
15:04:08     INFO -       2 CPUs
15:04:08     INFO -  Crash reason:  EXC_BAD_ACCESS / 0x0000000d
15:04:08     INFO -  Crash address: 0x0
15:04:08     INFO -  Thread 53 (crashed)
15:04:08     INFO -   0  CoreAudio + 0x1c7fe
15:04:08     INFO -      rbx = 0x00000001248bec00   r12 = 0x00000001248bec00
15:04:08     INFO -      r13 = 0x0000000000000000   r14 = 0x000000010c510c00
15:04:08     INFO -      r15 = 0x000000011e60f31c   rip = 0x00007fff839c07fe
15:04:08     INFO -      rsp = 0x000000010d326400   rbp = 0x000000010d326400
15:04:08     INFO -      Found by: given as instruction pointer in context
15:04:08     INFO -   1  CoreAudio + 0x1c762
15:04:08     INFO -      rip = 0x00007fff839c0763   rsp = 0x000000010d326410
15:04:08     INFO -      rbp = 0x000000010d326450
15:04:08     INFO -      Found by: stack scanning
15:04:08     INFO -   2  CoreAudio + 0x17b78
15:04:08     INFO -      rip = 0x00007fff839bbb79   rsp = 0x000000010d326460
15:04:08     INFO -      rbp = 0x000000010d3264c0
15:04:08     INFO -      Found by: stack scanning
15:04:08     INFO -   3  CoreAudio + 0x1b44b
15:04:08     INFO -      rip = 0x00007fff839bf44c   rsp = 0x000000010d326470
15:04:08     INFO -      rbp = 0x000000010d3264c0
15:04:08     INFO -      Found by: stack scanning
15:04:08     INFO -   4  CoreAudio + 0x1797f
15:04:08     INFO -      rip = 0x00007fff839bb980   rsp = 0x000000010d3264d0
15:04:08     INFO -      rbp = 0x000000010d326540
15:04:08     INFO -      Found by: stack scanning
15:04:08     INFO -   5  CoreAudio + 0x18298
15:04:08     INFO -      rip = 0x00007fff839bc299   rsp = 0x000000010d3264e0
15:04:08     INFO -      rbp = 0x000000010d326540
15:04:08     INFO -      Found by: stack scanning
See Also: → 847903
(In reply to TBPL Robot from comment #2)
The call stack is similar to that of bug 847903.
Depends on: 847903
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.