Closed Bug 693872 Opened 13 years ago Closed 9 years ago

[adbe 3501065]Firefox Crash [@ F_855855466_____________________ ] (Flash 11.0.1.152 and higher)

Categories

(External Software Affecting Firefox Graveyard :: Flash (Adobe), defect)

Product:
External Software Affecting Firefox Graveyard
Component:
Flash (Adobe)
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: marcia, Assigned: smadayag)

Details

(5 keywords)

Crash Data

Seen while looking at the explosive report. Seen across all versions on Windows only. All reports I looked at so far are running 11.0.1.152. https://crash-stats.mozilla.com/report/list?signature=F_855855466_____________________ https://crash-stats.mozilla.com/report/index/33ad2221-2175-40d8-bf40-815db2111010 Frame Module Signature [Expand] Source 0 NPSWF32.dll F_855855466_____________________ F_2002184587_____________________________________________________:2777 1 NPSWF32.dll F_2113118506__________________________________________________________________ F2134171444_________________________________________________________________________:186 2 NPSWF32.dll F_397880079__________________________ F_2002184587_____________________________________________________:2513 3 NPSWF32.dll F1994398563___________ F_2002184587_____________________________________________________:1315 4 NPSWF32.dll F430783468______________________ F_2002184587_____________________________________________________:2890 5 NPSWF32.dll F380954040____________________________________ F_1390094103_____________________________________________________:210 6 NPSWF32.dll F_1289021487_______________________________ F_1549700186____________________________________________:1838 7 NPSWF32.dll F_1995396427_________________ F_1549700186____________________________________________:12887 8 NPSWF32.dll F1546913566_____________________________________ F_1929819672___________________________________________________________________________:3822 9 NPSWF32.dll F957328252________________________ F_1929819672___________________________________________________________________________:508 10 user32.dll InternalCallWinProc 11 user32.dll UserCallWinProcCheckWow 12 user32.dll CallWindowProcAorW 13 user32.dll CallWindowProcW 14 xul.dll mozilla::plugins::PluginInstanceChild::FlashThrottleAsyncMsg::Run dom/plugins/ipc/PluginInstanceChild.cpp:1996 15 xul.dll MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:318 16 xul.dll MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:326 17 xul.dll MessageLoop::DoDelayedWork 18 xul.dll base::MessagePumpForUI::DoRunLoop ipc/chromium/src/base/message_pump_win.cc:219 19 xul.dll base::MessagePumpWin::RunWithDispatcher ipc/chromium/src/base/message_pump_win.cc:53 20 xul.dll base::MessagePumpWin::Run ipc/chromium/src/base/message_pump_win.h:78 21 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:208 22 xul.dll MessageLoop::RunHandler 23 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:175 24 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:516 25 plugin-container.exe wmain toolkit/xre/nsWindowsWMain.cpp:107 26 plugin-container.exe __tmainCRTStartup crtexe.c:594 27 kernel32.dll BaseThreadInitThunk 28 ntdll.dll __RtlUserThreadStart 29 ntdll.dll _RtlUserThreadStart
Not sure if this will help. There's some examples using the latest stuff in flash at these pages : http://www.adobe.com/devnet/flashplayer/stage3d.html http://www.adobe.com/devnet/actionscript.html
Sal, we are seeing this only on Flash 11. Can you have someone on your side look into this?
Here is the plugin report that shows the breakdown in Firefox 7.0.1: https://crash-analysis.mozilla.com/chofmann/20111029/top-plugin-crashes-7.0.1.html.
Crash Signature: [@ F_855855466_____________________ ] → [@ F_855855466_____________________ ] [@ hang | F_855855466_____________________ ]
we are looking into it. we are tracking internally in #bug=3015141...
Assignee: nobody → smadayag
Status: NEW → ASSIGNED
Summary: Firefox Crash [@ F_855855466_____________________ ] (Flash Version 11.0.1.152) → [adbe 3015141]Firefox Crash [@ F_855855466_____________________ ] (Flash Version 11.0.1.152)
It's not #1 top Flash crasher in 8.0.
Component: Plug-ins → Flash (Adobe)
Product: Core → Plugins
QA Contact: plugins → adobe-flash
Version: Trunk → 11.x
s/not//
Keywords: topcrash
this bug was deferred out of the brannan release and reassigned to cyril, fp11.3, for further investigation and analysis...
This signature paired with mozilla::plugins::PPluginInstanceParent::CallPBrowserStreamConstructor - bug 566062 is the #4 hang pair on FF 9.0. https://crash-analysis.mozilla.com/rkaiser/2011-12-12/2011-12-12.firefox.9.0.flashhangdetails.html
Keywords: hang
This hang signature is very high up in early Firefox 11 data - #2 issue in yesterday's Flash data: https://crash-analysis.mozilla.com/rkaiser/2012-03-19/2012-03-19.firefox.release.11.0.components.html#.flash
This is still around and high in Flash 11.2.202.228
Summary: [adbe 3015141]Firefox Crash [@ F_855855466_____________________ ] (Flash Version 11.0.1.152) → [adbe 3015141]Firefox Crash [@ F_855855466_____________________ ] (Flash 11.0.1.152 and higher)
Over 5K crashes in the last week across all Firefox versions. Highest concentration of crashes in FF 12 and 13. 73% of crashes are in 11.2.202.235, and 11.3.300.257 version shows up now as about 5% of crashes.
we are seeing the signature in 11.4. are there any reported STRs by chance?
It's #9 top Flash crasher with Flash 11.6.602.155. See https://crash-analysis.mozilla.com/rkaiser/2013-01-26/2013-01-26.firefox.flash.11-6-602-155.html Here is a recent stack trace for bp-5c07577e-a529-41b0-8511-52b7b2130127: Frame Module Signature Source 0 NPSWF32_11_6_602_155.dll F_855855466_____________________ F1160103271____________________________________________________:2829 1 NPSWF32_11_6_602_155.dll F1161311034_______________________________ F1375334242____________________________________________________________________________________________:1486 2 NPSWF32_11_6_602_155.dll F_397880079__________________________ F1160103271____________________________________________________:2565 3 NPSWF32_11_6_602_155.dll F1994398563___________ F1160103271____________________________________________________:1451 4 NPSWF32_11_6_602_155.dll F430783468______________________ F1160103271____________________________________________________:2945 5 NPSWF32_11_6_602_155.dll F1469229215_________________________________________ F_600578477________________________________________________________:1403 6 NPSWF32_11_6_602_155.dll F_1860184299______________________________ F_600578477________________________________________________________:609 7 NPSWF32_11_6_602_155.dll F_1228567354___________________ F_600578477________________________________________________________:588 8 NPSWF32_11_6_602_155.dll F_458799790____________________ F1160103271____________________________________________________:675 9 NPSWF32_11_6_602_155.dll F_86711400_________________________________________________________ F1160103271____________________________________________________:1023 10 NPSWF32_11_6_602_155.dll F_367967799___________________________________________ F_888760368_______________________________________________________________:406 11 NPSWF32_11_6_602_155.dll F_699876258_________________________ F_888760368_______________________________________________________________:829 12 NPSWF32_11_6_602_155.dll F1924306529_________________________ F2139786968________________________________________________________:198 13 NPSWF32_11_6_602_155.dll F_655827159____________________________________ F1259580468_______________________________________________________________:311 14 NPSWF32_11_6_602_155.dll F_1614844570___________________________________________________________________ F_2097641766____________________________________________________:1952 15 NPSWF32_11_6_602_155.dll F_469756800_____________________________ F2139786968________________________________________________________:304 16 NPSWF32_11_6_602_155.dll F1482560607_____________________________________________________________________ F1273921448______________________________________________________________________________________:5337 17 NPSWF32_11_6_602_155.dll F869737464______________________________________________________________ F_1238084962_________________________________________________________:1914 18 NPSWF32_11_6_602_155.dll F457761304___________________ F_1164684736________________________________________________________:616 19 NPSWF32_11_6_602_155.dll F_1868034707____________________________________________________________________ F_1787082934_______________________________________________________________:69 20 NPSWF32_11_6_602_155.dll F2027251393_____________________________________________________________ F_1238084962_________________________________________________________:2079
If not counting hangs, this is the #2 crash on 11.6.602.161 beta after the rather generic bug 763444 signature. Sal, did Adobe find out anything about this one?
our internal bug has gone stale. we entered a fresh internal bug, #3501065, for review...
Summary: [adbe 3015141]Firefox Crash [@ F_855855466_____________________ ] (Flash 11.0.1.152 and higher) → [adbe 3501065]Firefox Crash [@ F_855855466_____________________ ] (Flash 11.0.1.152 and higher)
marcia_ would you be able to supply us with the an actual unsymbolicated binary dump file? our dev believes he may be able to identify the true backtrace with the binary dump.
Benjamin, re comment #17, what are our policies there? I understand you are dealing with the Flash folks around those issues like looking into minidumps. Sal, Marcia hasn't seen this crash on her computer AFAIK, so all the minidumps we have are from users, and due to privacy reasons, we probably need to jump through some hoops there.
Adobe has executed an agreement so that a set of their engineers can come to a Mozilla office and debug minidumps directly. Talk to jeclark for details?
Jeromie, this is still showing up a top crash in current Flash versions (and has for a while). Are those stacks helpful to you at all, or there anything we or you can do about this one?
Flags: needinfo?(jeclark)
We've made a significant effort to resolve this issue, but have been unable to make meaningful progress. I'm happy to share technical details offline, but long story short, Minidumps aren't going to help. We examined a large number of relevant stacks, but our main takeaway was that this looks like a signature with multiple root-causes. Without STRs or at least URLs that may show us how to invoke the problem, we're flying blind. In order to effect a meaningful resolution, we need to get our hands on an interactive debug session. We're engaged in some new hardening efforts that we hope may surface this and similar issues; however, we have no direct way to identify and fix the issue at this time.
Flags: needinfo?(jeclark)
Keywords: topcrash-plugin
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: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 11.x → unspecified
I'm restricting comments on this old bug because of spam.
Restrict Comments: true
Product: External Software Affecting Firefox → External Software Affecting Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.