Closed Bug 697739 Opened 13 years ago Closed 9 years ago

Crash in F880614993________________________________

Categories

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

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

Tracking

(Not tracked)

Status:
RESOLVED INCOMPLETE

People

(Reporter: rob1weld, Unassigned, NeedInfo)

References

Details

(Keywords: crash)

Crash Data

Reported via the Link in: bp-829316ff-a438-4c23-a6ce-3c34c2111027 . The last two days I have had 1 BSOD each day, and thus the "Error Reporter" gets no chance. These BSODs are very rare and started two days ago. This BR is the only one for "[@ NtGdiDdLock ]". The symptoms are: slow startup loading over 200 Tabs progressing to a hang (even of the OS and Window's Task Manager), after a minute I get a BSOD for watchdog.sys . I suspect that [@ NtGdiDdLock ] might have occurred, (once) when I crashed and was lucky enough to have 'enough juice' (not running too slow), to trigger the Error Reporter and exit nicely. If [@ NtGdiDdLock ] is not related to the BSOD issue then it stands alone and this is the Thread for it.
Correcting the crash field. No other users have reported this specific crash. Have you installed any new addons lately?
Crash Signature: bp-829316ff-a438-4c23-a6ce-3c34c2111027 → [@ NtGdiDdLock ]
(In reply to Marcia Knous [:marcia] from comment #1) > Correcting the crash field. No other users have reported this specific > crash. Have you installed any new addons lately? Thanks. No "new" add-ons, but TM+ was updated. The crash has not reoccurred in the last few hours. I also have bp-cc9c2c14-f88c-4174-81a8-35c492111027 which is _slightly_ different since it is called "[@ hang | NtGdiDdLock ]".
Crash Signature: [@ NtGdiDdLock ] → [@ NtGdiDdLock ] [@ hang | NtGdiDdLock ]
(In reply to Marcia Knous [:marcia] from comment #1) > No other users have reported this specific crash. Reporting is "opt-in" (is it not?), the User must take at least one and perhaps two specific actions (enable Crash Reporting, AND click on the crash in about:crashes) to _actually_ report the crash. Another one: bp-6a2eca47-6fa7-4100-a30d-175f02111109, over a week apart; so it is not a common crash (for me). There is also a Bug filed against NPSWF32.dll (which is a common factor (and would require the User to have updated Plugins, which not everyone does)) which is Bug 698317.
Signature hang | NtGdiDdLock UUID efb12288-9756-4d06-adf9-39c0b2111130 Date Processed 2011-11-30 09:43:01.102385 Process Type plugin Version: Filename: NPSWF32.dll Uptime 2177 Install Age 3.0 weeks since version was first installed. Install Time 2011-11-09 17:36:23 Product Firefox Version 8.0 Build ID 20111104165243 Release Channel release OS Windows NT OS Version 5.1.2600 Service Pack 3 Build Architecture x86 Build Architecture Info AuthenticAMD family 15 model 107 stepping 2 Crash Reason EXCEPTION_BREAKPOINT Crash Address 0x7c90e514 App Notes AdapterVendorID: 10de, AdapterDeviceID: 0614, AdapterDriverVersion: 6.14.11.7824 D3D10 Layers? D3D10 Layers- D3D9 Layers? D3D9 Layers- EMCheckCompatibility True Frame Module Signature [Expand] Source 0 ntdll.dll KiFastSystemCallRet 1 gdi32.dll NtGdiDdLock 2 d3d9.dll DdLock 3 d3d9.dll CDriverSurface::InternalLockRect 4 d3d9.dll CDriverSurface::LockRect 5 NPSWF32.dll F880614993________________________________ F291219625_________________________________________________:2900 6 NPSWF32.dll F1911513206_____________________________ F291219625_________________________________________________:2822 7 NPSWF32.dll F799675765________________________________________________________________________________________________ F389709806________________________________________:3241 8 NPSWF32.dll F_1675047243__________________________________________________________________________________________ F389709806________________________________________:3539 9 NPSWF32.dll F745443706________________________________________________ F_502805826________________________________________:3850 10 NPSWF32.dll F_583365836_____________________________ F_502805826________________________________________:5136 11 NPSWF32.dll F450165255___________________________ F_502805826________________________________________:6127 12 NPSWF32.dll F1295919189______________________________________ F723216689_________________________________________:1823 13 NPSWF32.dll F_1311131038_________________________________________ F723216689_________________________________________:3548 14 NPSWF32.dll F_2025036863______________________ F_1055812748____________________________________:12049 15 NPSWF32.dll F_1995396427_________________ F_1055812748____________________________________:12879 16 NPSWF32.dll F1546913566_____________________________________ F806924378_____________________________________________________________________:3928 17 NPSWF32.dll F1185421069_____________________________ F806924378_____________________________________________________________________:332 18 user32.dll InternalCallWinProc 19 user32.dll UserCallWinProcCheckWow 20 user32.dll CallWindowProcAorW 21 user32.dll CallWindowProcW 22 xul.dll mozilla::plugins::PluginInstanceChild::FlashThrottleAsyncMsg::Run dom/plugins/ipc/PluginInstanceChild.cpp:1966 23 xul.dll MessageLoop::RunTask ipc/chromium/src/base/message_loop.cc:345 24 xul.dll MessageLoop::DeferOrRunPendingTask ipc/chromium/src/base/message_loop.cc:353 25 xul.dll MessageLoop::DoDelayedWork 26 xul.dll base::MessagePumpForUI::DoRunLoop ipc/chromium/src/base/message_pump_win.cc:219 27 xul.dll base::MessagePumpWin::RunWithDispatcher ipc/chromium/src/base/message_pump_win.cc:53 28 xul.dll base::MessagePumpWin::Run ipc/chromium/src/base/message_pump_win.h:78 29 xul.dll MessageLoop::RunInternal ipc/chromium/src/base/message_loop.cc:221 30 xul.dll MessageLoop::RunHandler 31 xul.dll MessageLoop::Run ipc/chromium/src/base/message_loop.cc:179 32 xul.dll XRE_InitChildProcess toolkit/xre/nsEmbedFunctions.cpp:516 33 plugin-container.exe wmain toolkit/xre/nsWindowsWMain.cpp:107 34 plugin-container.exe __tmainCRTStartup obj-firefox/memory/jemalloc/crtsrc/crtexe.c:591 35 kernel32.dll BaseProcessStart NPSWF32.dll 11.1.102.55 AEBCF68A3E74455994C9CCE79744EF541 NPSWF32.pdb
Severity: normal → critical
Status: UNCONFIRMED → NEW
Component: General → Flash (Adobe)
Ever confirmed: true
Keywords: crash
Product: Firefox → Plugins
QA Contact: general → adobe-flash
Summary: [@ NtGdiDdLock ] -- Nightly 10.0a1 → Crash in F880614993________________________________
Version: 10 Branch → 11.x
Blocks: 722614
No longer blocks: 722614
Depends on: 722614
6 Months old. Have not seen this reoccur this year. If the other Posters in this Thread wish to close this be my guest.
There are 87 crashes across all Firefox versions over the last four weeks. Flash 11.2.202.235 is still affected.
I haven't been having it happen nearly as much as I used to, but it still happens on occasion. I think it *might* be in some way related to the cache, since I usually don't get it until after I've played several flash files on that session, and I don't think I've ever had it occur when playing a video that was just a music clip with a static image placeholder to justify it being a video. However, not having done programming of any sort for the past four years, I have no idea how to go about verifying this.
(In reply to banjo2E from comment #7) > I haven't been having it happen nearly as much as I used to, but it still > happens on occasion. I think it *might* be in some way related to the cache, > since I usually don't get it until after I've played several flash files on > that session, and I don't think I've ever had it occur when playing a video > that was just a music clip with a static image placeholder to justify it > being a video. However, not having done programming of any sort for the past > four years, I have no idea how to go about verifying this. Speak of the devil; it just happened again yesterday. The problem with this bug is that it has a tendency to freeze systems entirely, which means crash reports aren't generated. My most recent entry in about:crashes is from over a month ago, and was throttled anyway. I'm beginning to suspect it may be graphics card/driver related. I happen to have a GeForce 8500GT and am using a driver from over a year ago ( http://www.nvidia.com/object/winxp-270.61-whql-driver.html ) since all of the drivers that came after it fail to install on my system and nobody I contact about said installation issues ever gets back to me.
It happened again just now, two videos and five minutes after opening Firefox on a fresh boot. Is there any way to generate a crash report manually? Most of the crashes from this bug (at least for me, and assuming this bug and 722614 are the same issue) don't generate reports due to causing complete system freezes.
It has something to do with Direct3D9. Update your graphics drivers or disable HW acceleration.
Quick update on my version of the problem. I discovered that Flash has, for some time, had a flawed implementation of a feature called "Protected Mode" and was advised to disable it by editing a config file. After doing so, I've had no problems with anything using Flash stuttering or causing crashes, at all. Forum topic about it linked below, if you're interested. I find it amusing that I found out how to fix this only after switching to a different Firefox fork. http://forum.palemoon.org/viewtopic.php?f=1&t=922
Searching the Internet I came up with this Solution (for OLD Computers) which reduces the chance of "false" (self-fixable) WatchDog Events from BSODing you. ----- Watchdog.sys The watchdog defines a time threshold. If a thread spends more time in a display driver than the threshold specifies, the watchdog tries to recover by switching to VGA graphics mode. If the attempt fails, the watchdog generates bug check 0xEA, THREAD_STUCK_IN_DEVICE_DRIVER. To disable timeout recovery, create the following REG_DWORD entry in the Registry, and set its value to 0: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog\Display\EaRecovery HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Watchdog\Display BreakPointDelay To disable the timer it is possible to add a new DWORD key named "DisableBugCheck”, with the value 1. Put the value at 0 to go back to normal. I did NOT enable this potential solution, yet. To control the tolerable thread delay, add a new DWORD key named "BreakPointDelay”, with the value of x where x * 10 seconds computes the limit. I configured my system for delays up to 30 seconds, so this key’s value is set to 3. ----- Now I either get no 'quick Watchdog BSODs' or I get a hang for 30 seconds and then a BSOD. I prefer this since if there is any chance of getting an Interrupt to fire and reset the Watchdog Timer I'll take that over a BSOD. With a fast Computer your 'saving Interrupt' MIGHT fire soon enough to reset the Watchdog Timer and eliminate the BSOD. ----- PS: Banjo2E I have an OLD NVidia Card and there was a point in time a yaer or two ago where I was unable to install NEWer Drivers. I started XP in Administrator Mode and ran the Installer as the Administrator (bypassing a File Write Protection). The "problem" is that the NEW Driver does not want to overwrite some of the OLD Driver's files that had a high permission level than the newer files. Once you get past the 'hump' you can install NEW Drivers on a very old Card (the NEW Drivers still support very old Cards, they just do not add new Features and extremely seldom can it fix Bugs (since there seems to be none left to fix)).
(In reply to Rob from comment #12) > Searching the Internet I came up with this Solution (for OLD Computers) > which reduces the chance of "false" (self-fixable) WatchDog Events from > BSODing you. > ... Doing the above has worked quite well. The number of BSODs I get seems greatly reduced and now I get much more 'Hang Reports' from about:crashes . bp-hr-20130303-b6d4088f-b7f4-4774-b2bd-a77be14f65c0 3/3/2013 06:59 bp-hr-20130223-6cc3c77d-fee9-4db1-8822-357f75aa7ad8 2/22/2013 22:17 bp-hr-20130222-4f6048a3-43eb-4ef0-a112-08901f0b1375 2/22/2013 06:50 bp-hr-20130222-d32109ed-c0a0-427c-8681-a6527255b473 2/22/2013 06:37 bp-hr-20130222-2969072e-f640-4341-bfdf-b803946d00db 2/22/2013 06:28 bp-hr-20130222-fc65b151-34fd-495d-8ed7-5b1e8e9d7932 2/22/2013 06:24 ff684912-10de-44df-8096-cb67035bc161 2/22/2013 05:57 bp-hr-20130222-2e70cf89-8a79-4a44-b198-05c4035717db 2/22/2013 05:41 bp-a8075da9-fd77-47c9-b738-b38692130221 2/21/2013 09:54
Flash 11.6.602.168 has known vulnerabilities. Please update: https://www.mozilla.org/plugincheck/
Crash Signature: [@ NtGdiDdLock ] [@ hang | NtGdiDdLock ] → [@ NtGdiDdLock ] [@ hang | NtGdiDdLock ] [@ hang | NtRequestWaitReplyPort]
I always try to make sure everything on my Computer is up to date. In the event that you spot something not-updated it is often only awaiting the interval for the Update-Checker to kick in. Yesterday I found the cause of _some_ of these Problems (but not necessarily THIS particular one). When Playing Videos (Flash or otherwise) and you have the DivX Codec (or Player) installed it installs an Update-Checker. When I run (other) Player Programs than use the DivX Filter the Update-Checker OFTEN triggers an Exception. (Running without the Debugger BSODs). Investigating.
I am the Reporter, and this was reported on 2011-10-27. I previously suggested closing it. In Comment 6 scoobidiver opposed closing this and has done some work on this. His name is 'marked' (changed) as "away", so I will "needmoreinfo" him. I am not opposed to this being closed, but will leave it open.
Flags: needinfo?(scoobidiver)
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
Closed: 9 years ago
Resolution: --- → INCOMPLETE
Version and milestone values are being reset to defaults as part of product refactoring.
Version: 11.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.