TopCrash Number #15 for 3.6.3 http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=NPSWF32.dll%400xb0b0d&version=Firefox%3A3.6.3 with latest plugin from the report it looks like this happens on russian ? sites.
Picking this up. The crash logs look bogus at the top. How can you tell that this is the latest Player build? Can you point the mdmp at the symbol data we've submitted for the latest Player?
Signature NPSWF32.dll@0xb0b0d UUID 4cdb1427-f51e-4f9c-a941-d80292100605 Time 2010-06-05 02:40:37.149761 Uptime 103 Last Crash 48408 seconds before submission Product Firefox Version 3.6.3 Build ID 20100401080539 Branch 1.9.2 OS Windows NT OS Version 5.1.2600 Service Pack 3 CPU x86 CPU Info GenuineIntel family 6 model 15 stepping 13 Crash Reason EXCEPTION_ACCESS_VIOLATION Crash Address 0x4 User Comments Related Bugs Crashing Thread Frame Module Signature [Expand] Source 0 NPSWF32.dll NPSWF32.dll@0xb0b0d 1 NPSWF32.dll NPSWF32.dll@0x200ead 2 NPSWF32.dll NPSWF32.dll@0x16042d 3 NPSWF32.dll NPSWF32.dll@0x160e89 4 NPSWF32.dll NPSWF32.dll@0x16039e 5 NPSWF32.dll NPSWF32.dll@0xe46e9 6 NPSWF32.dll NPSWF32.dll@0xf28ca 7 @0xfffffffe 8 nspr4.dll dtoa nsprpub/pr/src/misc/prdtoa.c:2825 9 nspr4.dll dtoa nsprpub/pr/src/misc/prdtoa.c:2825 10 user32.dll StringDuplicateW 11 user32.dll CallHookWithSEH 12 user32.dll CallHookWithSEH 13 user32.dll __fnHkINLPMSG 14 user32.dll __fnHkINLPMSG 15 ntdll.dll KiUserCallbackDispatcher 16 MSCTF.dll SysShellProc 17 user32.dll CallHookWithSEH 18 user32.dll NtUserCallNextHookEx 19 user32.dll FlipUserTextOutW 20 mzvkbd3.dll mzvkbd3.dll@0x17ef Filename Version Debug Identifier Debug Filename NPSWF32.dll 10.0.45.2 jethro: yes, we do have access to a .dmp, i'm not sure where your symbols are. if someone points me to them, i can look.
We have symbols for 10.0.45.2 on the symbol server. However, if you look at the "Modules" tab of that crash report, note that the flash player DLL does not list a module ID. For whatever reason, that DLL isn't providing the information necessary for our crash reporting system to find the symbols that correlate with it.
We won't be able to update the DLL already in the field, but I can make sure future Flash Players have this info. Can you tell me which field your reporting system sniffs for as a "Debug Identifier?" Thanks, JV
I don't think it's anything you're doing wrong, since we have symbols for lots of Flash crashes. It could be something particular to this crash or the user's system that caused this data to be missing. (The actual GUID is pulled from the CodeView record embedded in the binary.)
With Flash debug symbols, if these crashes still exist, they will be tracked in another bug. I close it as invalid.