Closed Bug 581184 Opened 15 years ago Closed 9 years ago

crash [@ F_964402326_______________________________________]

Categories

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

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: timeless, Assigned: smadayag)

References

()

Details

(Keywords: crash)

Crash Data

Signature F_964402326_______________________________________ UUID 7b4eaddd-fc4d-4c5d-bbc9-876e42100722 Time 2010-07-22 12:39:20.281889 Uptime 24638 Last Crash 438617 seconds (5.1 days) before submission Install Age 110429 seconds (1.3 days) since version was first installed. Product Firefox Version 3.6.7 Build ID 20100713130626 Branch 1.9.2 OS Windows NT OS Version 5.1.2600 Service Pack 3 CPU x86 CPU Info GenuineIntel family 15 model 6 stepping 5 Crash Reason EXCEPTION_ACCESS_VIOLATION Crash Address 0x15c User Comments Processor Notes EMCheckCompatibility False Crashing Thread Frame Module Signature [Expand] Source 0 NPSWF32.dll F_964402326_______________________________________ F1594236053________________________________________:1991 1 NPSWF32.dll F1401221563___________________________________________ F816923628_____________________________________________:13076 2 NPSWF32.dll F450165255___________________________ F816923628_____________________________________________:4674 3 NPSWF32.dll F1295919189______________________________________ F2042946143____________________________________________:1802 4 NPSWF32.dll F_1311131038_________________________________________ F2042946143____________________________________________:3441 5 NPSWF32.dll F_2025036863______________________ F1602437284_________________________________________:11121 6 NPSWF32.dll F_1995396427_________________ F1602437284_________________________________________:11974 7 NPSWF32.dll F1546913566_____________________________________ F_1343382264_______________________________________________________________________:3838 8 NPSWF32.dll F1185421069_____________________________ F_1343382264_______________________________________________________________________:268 9 user32.dll InternalCallWinProc 10 user32.dll UserCallWinProcCheckWow 11 user32.dll CallWindowProcAorW 12 user32.dll CallWindowProcW 13 xul.dll ProcessFlashMessageDelayed modules/plugin/base/src/nsPluginNativeWindowWin.cpp:174 14 xul.dll PluginWndProc modules/plugin/base/src/nsPluginNativeWindowWin.cpp:343 15 user32.dll InternalCallWinProc 16 user32.dll UserCallWinProcCheckWow 17 user32.dll DispatchMessageWorker 18 user32.dll DispatchMessageW 19 xul.dll nsAppShell::ProcessNextNativeEvent widget/src/windows/nsAppShell.cpp:179 20 winmm.dll timeGetTime 21 xul.dll nsBaseAppShell::OnProcessNextEvent widget/src/xpwidgets/nsBaseAppShell.cpp:311 22 xul.dll nsThread::ProcessNextEvent xpcom/threads/nsThread.cpp:508 23 xul.dll mozilla::ipc::MessagePump::Run ipc/glue/MessagePump.cpp:142 24 xul.dll xul.dll@0x9ac40f 25 xul.dll MessageLoop::RunHandler ipc/chromium/src/base/message_loop.cc:199 26 xul.dll nsComponentManagerImpl::GetServiceByContractID xpcom/components/nsComponentManager.cpp:2199 27 xul.dll xul.dll@0x30a8e3 28 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:173 29 xul.dll nsBaseAppShell::Run widget/src/xpwidgets/nsBaseAppShell.cpp:174 30 xul.dll nsAppStartup::Run toolkit/components/startup/src/nsAppStartup.cpp:183 31 nspr4.dll nspr4.dll@0xbdcf 32 xul.dll XRE_main toolkit/xre/nsAppRunner.cpp:3483 NPSWF32.dll 10.1.53.64 547FB6F990234E7FAABA5DE4C9F5BB911
Internal bug entered - #bug=2674026
Assignee: nobody → smadayag
Status: NEW → ASSIGNED
@timeless - would you be able to dig up a URL associated with this crash?
the url looked like this: http://www.last.fm/user/????.??/library/tags?tag=??????+?????+????? tiakapan: I believe that the url encodes your username and a search, would you mind if we disclose it?
Hmmm, I'd rather the user name wasn't made public if that's what you're implying would happen, though the search part is acceptable. Is there another url to analyse instead? Now I cast my mind back, I don't think any of the 'plug in' crashes generated a bug report box. The bug report you have is the last ones recorded, but it's from the start of the month. I think the Firefox on this machine got so messed up after that, it became incapable of even following crash protocol.
the url should be enough to try some things. were there any particular steps that lead up to the crash? otherwise, not much can be done without reproducible steps.
http://www.last.fm/user/LAST.HQ/library/tags?tag=brutal+death+metal That url is fine to check on - it refers to someone else's publicly shown link. @smadayag: as I was saying above, I'm not even sure that last submitted report is even relevant to the plug in black hole I was in afterwards. Basically I couldnt browse *anywhere* usual for long (ebay, lastfm, hotmail etc) without getting a lonnnnng hang, eventually followed by the 'plug in container' box. Carry on! Thanks.
thanks much. i've added a note with the specific URL.
we can't seem to reproduce, would it be possible to get reproducible steps? also, how often are we seeing the issue?
Crash Signature: [@ F_964402326_______________________________________]
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: 10.x → unspecified
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.