Closed Bug 905902 Opened 10 years ago Closed 5 years ago
Crash while scrolling complex and big web pages
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release) Build ID: 20130815030203 Steps to reproduce: 1. Open large PDF files 2. Scroll around fast Actual results: Crash Expected results: Smooth Scrolling
ID: b450369b-3516-42a7-92b5-841932130816 Signature: igd10umd32.dll@0x1fcfb9
Provide PDF url or testcase, please. https://crash-stats.mozilla.com/report/index/b450369b-3516-42a7-92b5-841932130816
Severity: normal → critical
Crash Signature: igd10umd32.dll@0x1fcfb9 → [@ igd10umd32.dll@0x1fcfb9 ]
Version: Trunk → 26 Branch
http://www.iab.net/media/file/VASTv3.0.pdf Or some Google documents which have many pages.
It doesn't crash for me. 1) Could you paste here the graphics section of about:support. In addition, be sure your GPU drivers are up-to-date. 2) Could you try with HWA disabled. https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration
It shall be related to GFX or HW acceleration, but it doesn't crash often at FX24 stage. https://crash-stats.mozilla.com/report/index/abaaa1a2-a13c-41ad-a466-04ac62130822 https://crash-stats.mozilla.com/report/index/abaaa1a2-a13c-41ad-a466-04ac62130822
No crash for me either on 26.0a2 (2013-09-30), Win 7. Could you also please check to reproduce the problem: 1. using Firefox in safe mode (with your addons disabled): http://support.mozilla.com/kb/Safe+Mode 2. On a new, empty profile: http://support.mozilla.org/en-US/kb/Managing-profiles#w_starting-the-profile-manager
Got a random out of the blue crash with this signature on Win64 7 FX24 when a non-PDF web page was loading. I couldn't reproduce it though. https://crash-stats.mozilla.com/report/index/4721d484-e41e-4652-a6d2-1e98a2131016
It doesn't crash much in safe mode, but still hit one. https://crash-stats.mozilla.com/report/index/39afd774-0f12-49b9-9b58-601fe2131017
Yet another one. It doesn't have the same signature as the original bug reports though. https://crash-stats.mozilla.com/report/index/9429a529-15f8-426e-aafc-f48ee2131017
Perhaps you can provide another URL where this is 100% reproducible
In safe mode, HWA is disabled. So the crashes are probably here. Did you update your Intel drivers?
(In reply to Paul Silaghi, QA [:pauly] from comment #12) > Perhaps you can provide another URL where this is 100% reproducible Finally, just find a page that constantly crashes my browser: http://nodeos.github.io/ I did noticed there is a biiiiiiig image on that page which made me thinking if it's due to the large texture size? https://crash-stats.mozilla.com/report/index/bp-76b5c6b9-92b9-461f-bb52-118362131022
(In reply to Loic from comment #13) > In safe mode, HWA is disabled. So the crashes are probably here. > > Did you update your Intel drivers? I think it's the latest WHQL driver from Intel (Thinkpad X220)
(In reply to WL from comment #14) > Finally, just find a page that constantly crashes my browser: > http://nodeos.github.io/ Can't reproduce on FF 27.0a1 2013-10-21 Win 7 x64
(In reply to WL from comment #15) > (In reply to Loic from comment #13) > > In safe mode, HWA is disabled. So the crashes are probably here. > > > > Did you update your Intel drivers? > > I think it's the latest WHQL driver from Intel (Thinkpad X220) The latest for Intel® HD graphics Driver for Windows 7 is 126.96.36.199.3223 (8/18/2013), maybe you could try to update yours. Can you test with HWA disabled, please. https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration
I've had 7 crashes in Aurora over the last 5 weeks with this signature. I don't believe Lenovo has released a more recent driver, so I've disabled HWA and will report back in a few weeks whether the crashes have ceased or not. FWIW, here's the latest crash: https://crash-stats.mozilla.com/report/index/56bb9365-b2a3-4722-b468-152e72140620 And my graphics info from about:support: Adapter Description Intel(R) HD Graphics 3000 Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter RAM Unknown Device ID 0x0126 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.16571) Driver Date 8-21-2012 Driver Version 188.8.131.5243 GPU #2 Active false GPU Accelerated Windows 13/13 Direct3D 11 (OMTC) Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics 3000 Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote true AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0
Andy, your Intel drivers are old, you should try to update them. The last ones are https://downloadcenter.intel.com/Detail_Desc.aspx?agr=Y&DwnldID=23763&lang=eng (4/10/2014, 184.108.40.20617)
(In reply to Loic from comment #19) I've actually tried to update the drivers in the past, but the Intel installer always quit and directed me to the OEM (Lenovo) for their latest customized drivers (which are ancient). I just ran Intel's online update check and it again told me: "A customized computer manufacturer driver is installed on your computer. The Intel Driver Update Utility is not able to update the driver. Installing a generic Intel driver instead of the customized computer manufacturer driver may cause technical issues. Contact your computer manufacturer for the latest driver for your computer." It's been a few months since I last ignored that warning and tried Intel's installer, so I just pulled down the latest (actually v 220.127.116.11.3517, since this is a 64-bit OS) and ran it. Lo and behold it seems to have installed! I'll cross my fingers and try to reboot this machine tonight. Assuming it boots, I'll reenable Hardware Acceleration and monitor for a few more weeks. I've been using this machine far less than normal over the last 2 weeks (took a vacation) but just for the record there haven't been any crashes with this bug's signature since I disabled HWA on 6/24. I would not consider that proof by any stretch (no STR, relatively short time monitoring for a random crash), but it's at least consistent with the hypothesis that HWA is involved.
I officially don't get Intel's versioning. After running their (not Lenovo's) latest driver installer, only the final number in the driver version changed (from 2843 to 3517). At any rate, HWA is reenabled. For posterity, this is my current UA: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:32.0) Gecko/20100101 Firefox/32.0 ... and Graphics info: Adapter Description Intel(R) HD Graphics 3000 Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter RAM Unknown Device ID 0x0126 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.16571) Driver Date 3-20-2014 Driver Version 18.104.22.16817 GPU #2 Active false GPU Accelerated Windows 11/11 Direct3D 10 Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics 3000 Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote false AzureCanvasBackend direct2d AzureContentBackend direct2d AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0
@Andy: If you know some websites where Firefox crashes, can you test again, please. @WL: did you meet the crashes again? Did you update your graphics driver?
Opening several pages of report data (large tables) in background tabs while scrolling through another complex page in Salesforce.com seemed to potentially be the trigger, but that's also typical of my work life and could just be luck or observation bias. I've also had several crashes with other signatures that, per the related bugs, appear to be caused by the new cycle collector (which I believe was just disabled in 32), so I may be misremembering which crash was which. If I get another crash with this signature I'll try to get better info about exactly which pages I was interacting with and/or opening at the time. Even in that produces a repeatable test case on my end, though, if it involves Salesforce.com then I won't be able to give others viable STR.
I reproduced the crash on Firefox 33 RC on Windows 7 32bit. Here is the crash report: https://crash-stats.mozilla.com/report/index/bp-9e49b52e-6507-4251-9f52-ece542141008 . I had many sites opened (Facebook, Youtube, Yahoo Mail, Pinterest, Google Play) and when I opened and navigated on Google Maps (on street view), crash occured. I don't have proper STR. In the last week 3001 crashes occured with this signature.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Bas, is this one of the OOMs we know about?
(In reply to Milan Sreckovic [:milan] (PTO 10/16-10/17) from comment #25) > Bas, is this one of the OOMs we know about? Not to my knowledge.
I turned hardware acceleration back on yesterday and it looks like it's causing out of memory issues: https://crash-stats.mozilla.com/report/index/7f183587-86d2-45e2-b501-fe2c72141028 This was on the Aurora 35.0a2 (2014-10-27) build. Here's my current graphics info from about:support... Adapter Description Intel(R) HD Graphics 3000 Adapter Drivers igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Adapter RAM Unknown Device ID 0x0126 Direct2D Enabled true DirectWrite Enabled true (6.2.9200.16571) Driver Date 3-20-2014 Driver Version 22.214.171.12417 GPU #2 Active false GPU Accelerated Windows 21/21 Direct3D 11 (OMTC) Subsys ID 21ce17aa Vendor ID 0x8086 WebGL Renderer Google Inc. -- ANGLE (Intel(R) HD Graphics 3000 Direct3D9Ex vs_3_0 ps_3_0) windowLayerManagerRemote true AzureCanvasBackend direct2d AzureContentBackend direct2d 1.1 AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0 According to Intel's website, that's the latest driver. That crash was actually the second time today that the browser content area went black, but I think I sidestepped an imminent crash the first time by having Aurora restart to apply the pending 10-27 update from yesterday. Unfortunately, I still have no consistent steps to reproduce beyond "Open a ton of complex pages in a ton of tabs and generally abuse Firefox all day."
This hardware has generally caused us problems with the recent changes, but usually not with the latest driver.
Crash Signature: [@ igd10umd32.dll@0x1fcfb9 ] → [@ igd10umd32.dll@0x1fcfb9 ] [@ igd10umd32.dll@0x1fd0b9 ]
Crash Signature: [@ igd10umd32.dll@0x1fcfb9 ] [@ igd10umd32.dll@0x1fd0b9 ] → [@ igd10umd32.dll@0x1fcfb9 ] [@ igd10umd32.dll@0x1fd0b9 ] [@ igd10umd32.dll@0x1fd399 ] [@ igd10umd32.dll@0x1fb1d9 ]
Here is a recent crash report in 34.0b8: https://crash-stats.mozilla.com/report/index/d2bcc130-4d79-4c45-9a20-3428c2141112 Maybe this crash should be in Graphics:Layers? crashing thread: 0 igd10umd32.dll igd10umd32.dll@0x1fcfb9 1 d3d10_1core.dll CBaseResource<ID3D10Texture1D, 2>::FinalConstruct(D3D10DDIARG_CREATERESOURCE const&, SD3D10SharedResourceCreationArgs const*, D3D10DDI_HRTRESOURCE) 2 d3d10_1core.dll CTexture2D<3>::FinalConstruct(STexture2DConstructorArgs const&) 3 d3d10_1core.dll CLayeredObject<CTexture2D<2> >::CreateInstance(STexture2DConstructorArgs const&, void*, void*, _GUID const&, void**) 4 d3d10_1core.dll CDevice::CreateLayeredChild(unsigned int, void const*, unsigned long, ILayeredUseCounted*, _GUID const&, void**) 5 d3d10_1core.dll CBridgeImpl<IDXGILayeredDevice, IDXGILayeredDevice, CLayeredObject<CDevice> >::CreateLayeredChild(unsigned int, void const*, unsigned long, ILayeredUseCounted*, _GUID const&, void**) 6 dxgi.dll CD3D10LayeredChild<ID3D10DeviceChild, CD3D10Device, 64>::FinalConstruct(ED3D10DeviceChildType, SLayeredArgs const*, unsigned long, ILayeredUseCounted*, _GUID const&) 7 dxgi.dll CD3D10DeviceChild<IDXGIResource>::FinalConstruct(ED3D10DeviceChildType, SLayeredArgs const*, unsigned long, ILayeredUseCounted*) 8 dxgi.dll CD3D10Resource::FinalConstruct(CD3D10Resource::TConstructorArgs const&) 9 dxgi.dll CLayeredObject<CD3D10Resource>::CreateInstance(CD3D10Resource::TConstructorArgs const&, void*, void*, _GUID const&, void**) 10 dxgi.dll CD3D10Resource::LUCCompleteLayerConstruction()
WL's most recent crashes: bp-0d423285-180d-4981-8afd-ea8a62150212 NS_CycleCollectorSuspect3 bp-fc5b34d9-8a43-4ae5-a1fe-ca8c82150205 igd10umd32.dll@0x1fcfb9 bp-839ec228-3453-4ab6-95eb-1d09e2150204 mozilla::layers::YCbCrImageDataSerializer::InitializeBufferInfo(unsigned int, unsigned int, unsigned int, unsigned int, unsigned int, mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> ... bp-96b3a09e-c994-4603-8112-116e72150203 mozilla::layers::ChromeProcessController::InitializeRoot()
WL writes "I still use Firefox nightly, it doesn't crash like this once I have the gfx driver upgraded. But I'm not 100% sure if it's the root cause."
This is our #1 crash in the Intel driver accounting for 38.19% of crashes in igd10umd32.dll: > igd10umd32.dll@0x1fcfb9: 2833 crashes (24.81%) > igd10umd32.dll@0x1fd0b9: 775 crashes (6.79%) > igd10umd32.dll@0x1fd399: 355 crashes (3.11%) > igd10umd32.dll@0x1fb1d9: 397 crashes (3.48%) 100% of the crashes are on Windows 7 32-bit 47% of the crashes are on Intel driver version 126.96.36.199.43 35% of the crashes are on Intel Xeon E3-1200 v2/3rd Gen Core processor GPU Top drivers: 188.8.131.5243: 2057 crashes (47%) 184.108.40.20628: 679 crashes (16%) 220.127.116.1117: 366 crashes (8%) 18.104.22.16857: 312 crashes (7%) Given the impact on Intel users I suggest we just blacklist these old driver versions, particularly if this can be worked around by using the latest Intel driver.
QA Whiteboard: topcrash-intel
Can you tell (from telemetry perhaps?) how many people would be affected by blacklisting <= 2843?
(In reply to Bas Schouten (:bas.schouten) from comment #33) > Can you tell (from telemetry perhaps?) how many people would be affected by > blacklisting <= 2843? It's hard to say for sure. I cross referenced the driver versions from Socorro for *all* crashes with the data in David Anderson's telemetry dashboard. From this data it looks like 459,836 of 1,615,006 sessions (28.47%) are using Intel 22.214.171.12443 or older. I think it's safe to assume that the actual number of users affected is some order of magnitude greater.
Crash volume for signature 'igd10umd32.dll@0x1fcfb9': - nightly(version 50):0 crashes from 2016-06-06. - aurora (version 49):0 crashes from 2016-06-07. - beta (version 48):0 crashes from 2016-06-06. - release(version 47):4 crashes from 2016-05-31. - esr (version 45):41 crashes from 2016-04-07. Crash volume on the last weeks: W. N-1 W. N-2 W. N-3 W. N-4 W. N-5 W. N-6 W. N-7 - nightly 0 0 0 0 0 0 0 - aurora 0 0 0 0 0 0 0 - beta 0 0 0 0 0 0 0 - release 0 0 0 0 0 1 2 - esr 0 0 0 0 0 4 8 Affected platform: Windows
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.