Closed Bug 585913 Opened 15 years ago Closed 14 years ago

[adbe 2690466] Flash crash in [@ F957328252________________________ ]

Categories

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

defect
Not set
critical

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: Tobbi, Assigned: smadayag)

References

()

Details

(Keywords: crash, topcrash)

Crash Data

A user in the German support forum reported crashes in the Flash player plugin with the above signature. Those occur every time when playing a flash video. Crash report: http://crash-stats.mozilla.com/report/index/bp-5f96a0b1-44a2-4a68-b4a0-ed7122100810 Bug at Adobe's bugtracker (not publicly accessible): http://bugs.adobe.com/jira/browse/FP-5195
Signature F957328252________________________ UUID 5f96a0b1-44a2-4a68-b4a0-ed7122100810 Process Type plugin Version: Filename: NPSWF32.dll Time 2010-08-10 03:20:55.210929 Uptime 1534 Install Age 219961 seconds (2.5 days) since version was first installed. Product Firefox Version 4.0b2 Build ID 20100720190347 Branch 2.0 OS Windows NT OS Version 5.1.2600 Service Pack 3 CPU x86 CPU Info AuthenticAMD family 15 model 79 stepping 2 Crash Reason EXCEPTION_ACCESS_VIOLATION Crash Address 0x44c Email Address URL User Comments Processor Notes EMCheckCompatibility False Related Bugs --- 585913 NEW Flash crash in [@ F957328252________________________ ] Crashing Thread Frame Module Signature [Expand] Source 0 NPSWF32.dll F957328252________________________ F_1343382264_______________________________________________________________________:503 1 user32.dll InternalCallWinProc 2 user32.dll UserCallWinProcCheckWow 3 user32.dll CallWindowProcAorW 4 user32.dll CallWindowProcW 5 xul.dll mozilla::plugins::PluginInstanceChild::FlashThrottleAsyncMsg::Run dom/plugins/PluginInstanceChild.cpp:1658 6 xul.dll MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:339 7 xul.dll MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:347 8 xul.dll MessageLoop::DoDelayedWork 9 xul.dll base::MessagePumpForUI::DoRunLoop ipc/chromium/src/base/message_pump_win.cc:218 10 xul.dll base::MessagePumpWin::RunWithDispatcher ipc/chromium/src/base/message_pump_win.cc:52 11 xul.dll base::MessagePumpWin::Run ipc/chromium/src/base/message_pump_win.h:78 12 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:219 13 xul.dll MessageLoop::RunHandler 14 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:176 15 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:427 16 plugin-container.exe wmain toolkit/xre/nsWindowsWMain.cpp:120 17 plugin-container.exe __tmainCRTStartup obj-firefox/memory/jemalloc/crtsrc/crtexe.c:591 18 kernel32.dll BaseProcessStart Show/hide other threads NPSWF32.dll 10.1.53.64 547FB6F990234E7FAABA5DE4C9F5BB911 NPSWF32.pdb
Keywords: crash
internal bug entered. tracking in #2690466.
Assignee: nobody → smadayag
Status: NEW → ASSIGNED
Summary: Flash crash in [@ F957328252________________________ ] → [adbe 2690466] Flash crash in [@ F957328252________________________ ]
Issue pinpointed. This will be fixed in our next release.
There are still crashes with FP 10.1.85.3 and FF 3.6.12. Signature F957328252________________________ UUID 2cf84398-9053-4132-acb1-7c0832101104 Process Type plugin Version: Filename: NPSWF32.dll Time 2010-11-04 07:05:56.556818 Uptime 2646 Install Age 536767 seconds (6.2 days) since version was first installed. Product Firefox Version 3.6.12 Build ID 20101026210630 Branch 1.9.2 OS Windows NT OS Version 6.1.7600 CPU x86 CPU Info GenuineIntel family 6 model 23 stepping 10 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x44c Frame Module Signature [Expand] Source 0 NPSWF32.dll F957328252________________________ F1849591512__________________________________________________________________:503 1 user32.dll InternalCallWinProc 2 user32.dll UserCallWinProcCheckWow 3 user32.dll CallWindowProcAorW 4 user32.dll CallWindowProcW 5 xul.dll mozilla::plugins::PluginInstanceChild::FlashThrottleAsyncMsg::Run dom/plugins/PluginInstanceChild.cpp:1399 6 xul.dll MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:340 7 xul.dll MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:348 8 xul.dll MessageLoop::DoDelayedWork 9 xul.dll base::MessagePumpForUI::DoRunLoop ipc/chromium/src/base/message_pump_win.cc:218 10 xul.dll base::MessagePumpWin::RunWithDispatcher ipc/chromium/src/base/message_pump_win.cc:52 11 xul.dll base::MessagePumpWin::Run ipc/chromium/src/base/message_pump_win.h:78 12 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:216 13 xul.dll MessageLoop::RunHandler 14 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:173 15 xul.dll base::Thread::ThreadMain ipc/chromium/src/base/thread.cc:165 16 xul.dll `anonymous namespace'::ThreadFunc ipc/chromium/src/base/platform_thread_win.cc:26 17 kernel32.dll BaseThreadInitThunk 18 ntdll.dll __RtlUserThreadStart 19 ntdll.dll _RtlUserThreadStart NPSWF32.dll 10.1.85.3 A3F06758F9E74615BE208F6A332749EB1 NPSWF32.pdb
There are still crashes with FP 10.1.102.64 Signature F957328252________________________ UUID d0ad9db0-6cf8-4ca1-b4fc-ce2b62101109 Process Type plugin Version: Filename: NPSWF32.dll Time 2010-11-09 16:29:13.714414 Uptime 639 Install Age 24235 seconds (6.7 hours) since version was first installed. Product Firefox Version 4.0b8pre Build ID 20101109072504 Branch 2.0 OS Windows NT OS Version 5.1.2600 Service Pack 2 CPU x86 CPU Info GenuineIntel family 15 model 6 stepping 5 Crash Reason EXCEPTION_ACCESS_VIOLATION_READ Crash Address 0x24 App Notes AdapterVendorID: 10de, AdapterDeviceID: 01d3 Frame Module Signature [Expand] Source 0 NPSWF32.dll F957328252________________________ F58547254____________________________________________________________________:503 1 user32.dll InternalCallWinProc 2 user32.dll UserCallWinProcCheckWow 3 user32.dll CallWindowProcAorW 4 user32.dll CallWindowProcW 5 xul.dll mozilla::plugins::PluginInstanceChild::WinlessHiddenFlashWndProc dom/plugins/PluginInstanceChild.cpp:1810 6 user32.dll InternalCallWinProc 7 user32.dll UserCallWinProcCheckWow 8 user32.dll DispatchClientMessage 9 user32.dll __fnDWORD 10 ntdll.dll KiUserCallbackDispatcher 11 xul.dll mozilla::plugins::PluginInstanceChild::FlashThrottleMessage dom/plugins/PluginInstanceChild.cpp:1918 12 user32.dll NtUserPeekMessage 13 xul.dll mozilla::ipc::RPCChannel::WaitForNotify ipc/glue/WindowsMessageLoop.cpp:917 14 xul.dll mozilla::ipc::RPCChannel::Call ipc/glue/RPCChannel.cpp:201 15 xul.dll mozilla::plugins::PPluginModuleChild::CallNPN_UserAgent obj-firefox/ipc/ipdl/PPluginModuleChild.cpp:245 16 xul.dll mozilla::plugins::PluginModuleChild::GetUserAgent dom/plugins/PluginModuleChild.cpp:589 17 xul.dll mozilla::plugins::child::_useragent dom/plugins/PluginModuleChild.cpp:1159 18 NPSWF32.dll F1127609640_______________________________ F58547254____________________________________________________________________:2076 19 NPSWF32.dll F686385563_______________________________________________ F58547254____________________________________________________________________:593 20 NPSWF32.dll F510872805_____________________________________________________ F1973280565_______________________________________:182 21 NPSWF32.dll NPP_New F1989153418____________________________________________________________:534 22 xul.dll mozilla::plugins::PluginModuleChild::AnswerPPluginInstanceConstructor dom/plugins/PluginModuleChild.cpp:1766 23 xul.dll mozilla::plugins::PPluginModuleChild::OnCallReceived obj-firefox/ipc/ipdl/PPluginModuleChild.cpp:659 24 xul.dll mozilla::ipc::RPCChannel::DispatchIncall ipc/glue/RPCChannel.cpp:517 25 xul.dll mozilla::ipc::RPCChannel::Incall ipc/glue/RPCChannel.cpp:503 26 xul.dll mozilla::ipc::RPCChannel::OnMaybeDequeueOne ipc/glue/RPCChannel.cpp:434 27 xul.dll MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:343 28 xul.dll MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:351 29 xul.dll MessageLoop::DoWork ipc/chromium/src/base/message_loop.cc:451 30 xul.dll base::MessagePumpForUI::DoRunLoop ipc/chromium/src/base/message_pump_win.cc:213 31 xul.dll base::MessagePumpWin::RunWithDispatcher ipc/chromium/src/base/message_pump_win.cc:52 32 xul.dll base::MessagePumpWin::Run ipc/chromium/src/base/message_pump_win.h:78 33 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:219 34 xul.dll MessageLoop::RunHandler 35 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:176 36 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:506 37 plugin-container.exe wmain toolkit/xre/nsWindowsWMain.cpp:125 38 plugin-container.exe __tmainCRTStartup obj-firefox/memory/jemalloc/crtsrc/crtexe.c:591 39 kernel32.dll BaseProcessStart NPSWF32.dll 10.1.102.64 5BFFF4B3CC284B94A7DD3026F0CD791E1 NPSWF32.pdb
It is #4 top crasher in 3.6.12 for the last 3 days.
thanks. i've re-opened our internal bug and added the logs crashing in Salt.
I am the initial "german user" prompting this post... actually I don't get any flash crashes lately, however I spotted that some of the pages I had open when crashing apparently used flash data compiled in older flash versions (can't really say how old, I jsut noticed that I crashed when some ad-banners changed or refreshed and sent some of the pages a info note, they changed the ad-banners, and since then no crash) not sure however how that could help with solving the general problem as I am not really a techie. maybe the data is in the bug reports somewhere?
Keywords: topcrash
across all firefox releases there is quite a dramatic spike for this signature around nov 3. date crash_count for F957328252 20101031 3273 20101101 3272 20101102 3255 20101103 8668 20101104 9735 20101105 9078 20101106 8702 20101106 8702 20101107 8496 20101107 8496 20101108 8197 20101108 8197 20101109 9118 20101109 9118 20101110 10104 20101111 10306
Blocks: 616358
highest pct. of these are winXP, and are associated with flash 10.1.102.64, which was released on Nov 4. If updates of that release rolled out faster than usual and a high pct of users have moved up to 10.1.102.64 that would account for the higher volume there, but usually flash updates take longer and that would indicate a significant volume regression of this signature in the latest flash update. checking --- F957328252________________________ 20101201-crashdata.csv found in: 3.6.12 4.0b7 3.6.8 3.6.10 4.0b8pre 3.6.13 3.6.6 4.0b6 3.6.9 3.6.11 4.0b4 3.5.15 3.6.4 3.7a3pre 3.6.3 4.0b1 3.6 3.1b3 4.0b7pre 4.0b3 3.6.7 4.0b2 4.0b5 3.0.19 3.6.2 3.5.16 3.7a3 3.6.1 2pre 3.6b2 3.6.14pre 3.5b4 3.5.8 3.5.7 3.5.2 3.5.13 3.5.1 3.0b4 3.0.8 3.0.15 release total-crashes F957328252________________________ crashes pct. all 351617 11405 0.0324359 3.6.12 223644 8842 0.039536 4.0b7 35471 1162 0.0327592 3.6.8 8077 298 0.0368949 3.6.10 8936 248 0.0277529 4.0b8pre4573 145 0.0317079 3.6.13 3589 143 0.039844 3.6.6 3734 111 0.0297268 4.0b6 3102 77 0.0248227 .... os breakdown F957328252________________________Total 11367 Win5.1 0.72 Win6.0 0.12 Win6.1 0.16 flash versions around at time of crash 6354 10.1.102.64 2304 10.1.85.3 1393 10.1.82.76 1254 10.1.53.64 29 10.1.53.38 28 10.1.53.21 5 10.1.53.55
Yeah my bad I had my dates wrong I thought that was released on the 9th. Its possible to see a spike that quickly. We'll need some time to investigate.
Depends on: 519423
This is the #2 Windows crash in B8 with almost 6K in crashes.
This is the #4 overall crash in Beta 9 if you look at just the plugin crashes. Almost 3K crashes in one week.
We placed some guard code in Spicy, currently 10,2,152,32, and the issue is trending down. I beleive the first release of Spicy was Feb 8. A week sample had as many as Feb 1 - 70000+ hits Feb 15 - 59000+ hits Mar 1 - 46000+ hits Marking this Fixed, but will continue to monitor the signature.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by Flash 10.2.152.32]
4.0b12 correlations by Flash version confirm it is fixed in 10.2.152.32: F957328252________________________|EXCEPTION_ACCESS_VIOLATION_READ (709 crashes) 100% (709/709) vs. 22% (15217/68642) NPSWF32.dll 65% (463/709) vs. 4% (2947/68642) 10.1.102.64 10% (70/709) vs. 0% (334/68642) 10.1.53.64 11% (77/709) vs. 0% (291/68642) 10.1.82.76 12% (86/709) vs. 1% (360/68642) 10.1.85.3 1% (7/709) vs. 0% (25/68642) 10.2.151.49
Status: RESOLVED → VERIFIED
It is not fully fixed even if the crash volume is lower than before the patch landing: F957328252________________________|EXCEPTION_ACCESS_VIOLATION_READ (728 crashes) 1% (4/728) vs. 1% (1073/158636) 10.2.152.26 0% (1/728) vs. 1% (1590/158636) 10.2.152.32 1% (6/728) vs. 1% (2300/158636) 10.2.153.1 2% (11/728) vs. 4% (6452/158636) 10.2.159.1 1% (5/728) vs. 6% (9277/158636) 10.3.181.14
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Whiteboard: [fixed by Flash 10.2.152.32]
thank scoobidiver... we took a fix, so i've entered another bug to track the remaining crash issue. tracking in #bug=2887959. i'm currently looking for a wasabi crash incident and i've also update the title to reflect the new bug id.
Status: REOPENED → ASSIGNED
For reference... the old internal bug number is 2690466.
Summary: [adbe 2690466] Flash crash in [@ F957328252________________________ ] → [adbe 2887959] Flash crash in [@ F957328252________________________ ]
Crash Signature: [@ F957328252________________________ ]
after investigation our dev has pointed out that: ... although the obfuscated signature is the same, the actual crash in the function is on a different line... this is a new crash, not a re-appearance of the previous crash. we can track the new issue here if you would prefer, but when making queries, please try to separate the signature:495. else, we can close this out as fixed and track in another issue.
(In reply to comment #19) > we can close this out as fixed and track in another issue. I close again this one as fixed and open bug 664950.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
Summary: [adbe 2887959] Flash crash in [@ F957328252________________________ ] → [adbe 2690466] Flash crash in [@ F957328252________________________ ]
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.