We've had a crash with Firefox 24.3.0esrpre on OSX 10.8 while running Flash related tests with mozmill. Crash report: https://crash-stats.mozilla.com/report/index/afae650c-61ed-4a10-84ab-f67752140213
Crash Reason EXC_BAD_ACCESS / KERN_INVALID_ADDRESS Crash Address 0x0 0 FlashPlayer-10.6 FlashPlayer-10.6@0x8c9546 1 FlashPlayer-10.6 F_337042389_________ 2 FlashPlayer-10.6 FlashPlayer-10.6@0x8cd225 Andrei, I assume the latest version of Flash is installed on this box? Which test failed exactly? Is it reproducible on that machine?
Severity: normal → critical
(In reply to Henrik Skupin (:whimboo) from comment #1) > Andrei, I assume the latest version of Flash is installed on this box? As can be seen from the crash report yes, we are running the latest version: `Process Type plugin Shockwave Flash Version:188.8.131.52 Filename:Flash Player.plugin` > Which test failed exactly? I don't think the full log is relevant, so here is a snippet: > 02:29:47 TEST-START | testFlash_SWFVideoURL/test1.js | setupModule > 02:29:47 TEST-START | testFlash_SWFVideoURL/test1.js | testFlashURL > 02:41:10 WARNING: pipe error: Broken pipe: file /builds/slave/m-esr24-osx64-ntly-00000000000/build/ipc/chromium/src/chrome/common/ipc_channel_posix.cc, line 700 > 02:41:10 > 02:41:10 ###!!! [Parent][RPCChannel] Error: Channel error: cannot send/recv > 02:41:10 > 02:41:10 ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv > 02:41:10 > 02:41:10 > 02:41:10 ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv > 02:41:10 > 02:41:10 ###!!! [Parent][AsyncChannel] Error: Channel error: cannot send/recv > 02:41:10 TEST-PASS | testFlash_SWFVideoURL/test1.js | testFlashURL > 02:41:10 TEST-START | testFlash_SWFVideoURL/test1.js | teardownModule The affected test is `testFlash_SWFVideoURL/test1.js`: http://hg.mozilla.org/qa/mozmill-tests/file/mozilla-esr24/firefox/tests/endurance/testFlash_SWFVideoURL/test1.js > Is it reproducible on that machine? We haven't this crash with other versions. I'll run the test and come back.
So the test itself passed. Looks like something in teardown, which in this case is closeAllTabs(). So it could be an unload issue with Flash.
I wasn't able to reproduce this on the affected machine.
I'm closing a lot of bugs which are filed as Adobe Flash bugs which are either irrelevant, not actionable, or not serious enough to track in the Mozilla bug tracker. For the most part, Flash bugs should be filed in Adobe bugbase, and we'll only track a few highly-critical issues in the Mozilla tracker.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.