Closed Bug 1096864 Opened 10 years ago Closed 10 years ago

Black screen appears suddenly during browsing on Firefox 33.1 like in bug 1083071

Categories

(Core :: Graphics, defect)

33 Branch
x86_64
Windows 8.1
defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox33 + affected
firefox34 + unaffected
firefox35 + unaffected
firefox36 + unaffected

People

(Reporter: saurabh.nospam, Unassigned)

References

Details

(Keywords: regression)

Attachments

(4 files)

Attached image FFUIIssue.png
User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0
Build ID: 20141106120505

Steps to reproduce:

I Updated to Firefox 33.1 and then i started browsing for few mins
and suddenly i got black window in firefox.
Attached is the screen for the same.
My machine specs are
-Windows 8.1 x64
-Intel HD Graphics 4400(Driver Version:10.18.10.3960)

Let me know if you need more info.


Actual results:

Got Black window


Expected results:

Should work normally
It's bug 1083071 but it should be fixed in 33.1...

Could you type about:support in the location bar and paste the section "graphics", please.

In addition (and as possible workaround), could you test with OMTC disabled:
about:config > layers.offmainthreadcomposition.enabled = false (restart Firefox to apply)
Component: Untriaged → Graphics
Flags: needinfo?(saurabh.nospam)
Product: Firefox → Core
Summary: Black screen on firefox 33.1 → Black screen on Firefox 33.1 like in bug 1083071
(In reply to saurabh from comment #0)
> Should work normally

Can you run http://people.mozilla.org/~jmuizelaar/crash-firefox.exe, submit the crash, and then post the url from about:crashes?
(In reply to Jeff Muizelaar [:jrmuizel] from comment #2)
> (In reply to saurabh from comment #0)
> > Should work normally
> 
> Can you run http://people.mozilla.org/~jmuizelaar/crash-firefox.exe, submit
> the crash, and then post the url from about:crashes?

Just to confirm the blackness wasn't right away at startup? Does the blackness always happen at the same time?
(In reply to Loic from comment #1)
> Could you type about:support in the location bar and paste the section
> "graphics", please.

Graphics
--------

Adapter Description: Intel(R) HD Graphics Family
Adapter Drivers: igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
Adapter RAM: Unknown
Device ID: 0x0a16
Direct2D Enabled: true
DirectWrite Enabled: true (6.3.9600.17111)
Driver Date: 9-29-2014
Driver Version: 10.18.10.3960
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Vendor ID: 0x8086
WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote: true
AzureCanvasBackend: direct2d
AzureContentBackend: direct2d
AzureFallbackCanvasBackend: cairo
AzureSkiaAccelerated: 0

(In reply to Loic from comment #1)
> In addition (and as possible workaround), could you test with OMTC disabled:
> about:config > layers.offmainthreadcomposition.enabled = false (restart
> Firefox to apply)

I will try that and report my findings.



(In reply to Jeff Muizelaar [:jrmuizel] from comment #2)
> (In reply to saurabh from comment #0)
> > Should work normally
> 
> Can you run http://people.mozilla.org/~jmuizelaar/crash-firefox.exe, submit
> the crash, and then post the url from about:crashes?

Here it is
https://crash-stats.mozilla.com/report/index/421f7409-c3f8-4285-8f42-cfd972141112

(In reply to Jeff Muizelaar [:jrmuizel] from comment #3)
> (In reply to Jeff Muizelaar [:jrmuizel] from comment #2)
> > (In reply to saurabh from comment #0)
> > > Should work normally
> > 
> > Can you run http://people.mozilla.org/~jmuizelaar/crash-firefox.exe, submit
> > the crash, and then post the url from about:crashes?
> 
> Just to confirm the blackness wasn't right away at startup? Does the
> blackness always happen at the same time?
The blackness does not happen right away at startup it occurs after few mins of usage.
And no blackness does not happen at same time it occurs after few mins.
Flags: needinfo?(saurabh.nospam)
We have 2 reports about this issue on the French board: 
http://forums.mozfr.org/viewtopic.php?f=5&t=121096

The blackness appears randomly during browsing, after 20 min or 5 hours.
Attached image FF_black_window.png
Attached image about_support.png
Both users affected are on Windows 8.1, like the OP.
Summary: Black screen on Firefox 33.1 like in bug 1083071 → Black screen appears suddenly during browsing on Firefox 33.1 like in bug 1083071
Given what we've seen in bug 1083071, I'm going to assume that this impacts all channels. Happy to be proved wrong.
Another about:support:


    Accélération graphique
    Date du pilote 9-29-2014
    Date du pilote (GPU #2) 11-3-2014
    Description de la carte Intel(R) HD Graphics 4600
    Description de la carte (GPU #2) NVIDIA GeForce GTX 860M
    DirectWrite activé false (6.3.9600.17111)
    Fenêtres avec accélération graphique 0/1 Basic (OMTC)
    GPU #2 active false
    ID du périphérique 0x0416
    ID du périphérique (GPU #2) 0x119a
    ID du vendeur 0x8086
    ID du vendeur (GPU #2) 0x10de
    Pilote de la carte (GPU #2) nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
    Pilotes de la carte igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
    RAM de la carte Unknown
    RAM de la carte (GPU #2) 2048
    Rendu WebGL Google Inc. -- ANGLE (Intel(R) HD Graphics 4600 Direct3D9Ex vs_3_0 ps_3_0)
    Version du pilote 10.18.10.3960
    Version du pilote (GPU #2) 9.18.13.4465
    windowLayerManagerRemote true
    AzureCanvasBackend skia
    AzureContentBackend cairo
    AzureFallbackCanvasBackend cairo
    AzureSkiaAccelerated 0
Saurabh,

Can you post the make and model number of the computer that you're experiencing this on?
Flags: needinfo?(saurabh.nospam)
Also, can you try Firefox Nightly to see if the same problem happens?
A general search of Google (search using ntdll.dll 6.3.9600.17278 crash) shows that ntdll.dll (version 6.3.9600.17278) is causing a lot of crashes for others in various apps, not just browsers.
Same issue here. Installed Firefox 33.1 today on Microsoft Surface Pro running Windows 8.1 Pro. Also installed ad blocker add-on, but after the crashes started, removed it - still crashing.

Screen blackouts always occur between videos on YouTube playlists.
(In reply to iSofia from comment #14)
> Same issue here. Installed Firefox 33.1 today on Microsoft Surface Pro
> running Windows 8.1 Pro. Also installed ad blocker add-on, but after the
> crashes started, removed it - still crashing.
> 
> Screen blackouts always occur between videos on YouTube playlists.

Could you please type about:crashes into the URL bar and post a link to the most recent crash?
iSofia, please try Nightly to see if the problem still happens there.
Flags: needinfo?(sofiaism)
The most recent crash:

https://crash-stats.mozilla.com/report/index/ccaeed12-631d-4e8c-9f2f-3991b2141113
Flags: needinfo?(sofiaism)
(In reply to iSofia from comment #17)
> The most recent crash:
> 
> https://crash-stats.mozilla.com/report/index/ccaeed12-631d-4e8c-9f2f-
> 3991b2141113

Although this crash seems to have some relationship to bug 1072151, I see SPVC32.dll (Search Protect) popping up. Have you done a Malware scan lately with something like Malwarebytes?
(In reply to Arthur K. from comment #18)
> Although this crash seems to have some relationship to bug 1072151, I see
> SPVC32.dll (Search Protect) popping up. Have you done a Malware scan lately
> with something like Malwarebytes?

Could that be caused by the Adblocker plugin?
(In reply to Jeff Muizelaar [:jrmuizel] from comment #16)
> iSofia, please try Nightly to see if the problem still happens there.

I'm running the Nightly v36.0a1 (2014-11-13) now. 

So far, so good.
(In reply to iSofia from comment #19)
> (In reply to Arthur K. from comment #18)
> > Although this crash seems to have some relationship to bug 1072151, I see
> > SPVC32.dll (Search Protect) popping up. Have you done a Malware scan lately
> > with something like Malwarebytes?
> 
> Could that be caused by the Adblocker plugin?

Which Adblocker? Search Protect is a toolbar add-on that often sneaks in on the back of a regular software install.
(In reply to Arthur K. from comment #21)
> Which Adblocker?

It could either be Adblock Plus v2.6.6, or Adblock Edge v2.1.6, both downloaded and installed from Mozilla's add-ons site:

1. https://addons.mozilla.org/en-US/firefox/addon/adblock-plus/
2. https://addons.mozilla.org/en-US/firefox/addon/adblock-edge/

Can't be sure which one, because I tried them both.
So far, the Nightly build has been running the YouTube playlist for the past half hour with no issues. Just installed Adblock Plus v2.6.6 again to see if there are any issues.
(In reply to iSofia from comment #22)
> (In reply to Arthur K. from comment #21)
> > Which Adblocker?
> 
> It could either be Adblock Plus v2.6.6, or Adblock Edge v2.1.6, both
> downloaded and installed from Mozilla's add-ons site:
> 
> 1. https://addons.mozilla.org/en-US/firefox/addon/adblock-plus/
> 2. https://addons.mozilla.org/en-US/firefox/addon/adblock-edge/
> 
> Can't be sure which one, because I tried them both.

Neither of these would be suspect based on info in the crash data.
Nightly just crashed when I manually switched videos in the YouTube playlist:

https://crash-stats.mozilla.com/report/index/dde9fbac-37fc-4e61-a567-1af542141113
(In reply to iSofia from comment #25)
> Nightly just crashed when I manually switched videos in the YouTube playlist:
> 
> https://crash-stats.mozilla.com/report/index/dde9fbac-37fc-4e61-a567-
> 1af542141113

The signature has changed in this new crash. Could you try updating your Intel driver to version 3958 (https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24329&lang=eng&ProdId=3712) to see if it helps.
(In reply to Arthur K. from comment #26)
> The signature has changed in this new crash. Could you try updating your
> Intel driver to version 3958
> (https://downloadcenter.intel.com/Detail_Desc.
> aspx?DwnldID=24329&lang=eng&ProdId=3712) to see if it helps.

I don't follow; what could have caused the signature to change?
(In reply to iSofia from comment #27)
> (In reply to Arthur K. from comment #26)
> > The signature has changed in this new crash. Could you try updating your
> > Intel driver to version 3958
> > (https://downloadcenter.intel.com/Detail_Desc.
> > aspx?DwnldID=24329&lang=eng&ProdId=3712) to see if it helps.
> 
> I don't follow; what could have caused the signature to change?

Without knowing what's been changed since 33.1 and yesterday's nightly, it's as yet unclear. The previous crash was an OOM, the crash from 36 nightly was Compositor related. Your old driver (10.18.10.3496) isn't especially old which is why I suggested updating it to v3958 and seeing if it happens again on nightly. Any chance you could do that and try again?
Why is the discussion about crashing issues now?
(In reply to Jeff Muizelaar [:jrmuizel] from comment #11)
> Saurabh,
> 
> Can you post the make and model number of the computer that you're
> experiencing this on?

Sure.
I have HP Pavilion 15-n011TU.
Specs are 
Processor: Intel Core i5-4200U
Video : Intel HD Graphics 4400
RAM : 8 GB
Flags: needinfo?(saurabh.nospam)
(In reply to iSofia from comment #25)
> Nightly just crashed when I manually switched videos in the YouTube playlist:
> 
> https://crash-stats.mozilla.com/report/index/dde9fbac-37fc-4e61-a567-
> 1af542141113

Great. It seems very likely that this bug is duplicate of bug 1089364. I landed a fix for that today. I expect that the fix will be in tomorrows nightly. The build here http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-inbound-win32/1415914447/ has the fix. I would be very interested to see if you can reproduce the problem with that build.
Flags: needinfo?(sofiaism)
Depends on: 1089364
Nightly v36.0a1 (2014-11-13) crashed a number of times. Just installed Nightly v36.0a1 (2014-11-14).

Whoa! It crashed big time just as I was typing this message, and even brought Chrome down with it. Two open tabs, one running YouTube, and the other, GMail. Here's the report:

https://crash-stats.mozilla.com/report/index/149dcb00-aa83-41da-97d1-57aaa2141115
Flags: needinfo?(sofiaism)
(In reply to iSofia from comment #32)
> Nightly v36.0a1 (2014-11-13) crashed a number of times. Just installed
> Nightly v36.0a1 (2014-11-14).
> 
> Whoa! It crashed big time just as I was typing this message, and even
> brought Chrome down with it. Two open tabs, one running YouTube, and the
> other, GMail. Here's the report:
> 
> https://crash-stats.mozilla.com/report/index/149dcb00-aa83-41da-97d1-
> 57aaa2141115

Can you post some of the other crash report urls. This one seems like an unrelated problem having to do with the mp4 decoder.
Flags: needinfo?(sofiaism)
(In reply to Jeff Muizelaar [:jrmuizel] from comment #33)
> Can you post some of the other crash report urls. This one seems like an
> unrelated problem having to do with the mp4 decoder.

That was the only crash for Nightly v36.0a1 (2014-11-14). Before that, there were another two on Nightly v36.0a1 (2014-11-13):

https://crash-stats.mozilla.com/report/index/e569538b-fae0-4445-a214-21aca2141115
https://crash-stats.mozilla.com/report/index/1e5efd89-3ebb-41bb-bf76-1361c2141115
Flags: needinfo?(sofiaism)
Nightly should not be crashing anymore. Can you try again with a new one?
Flags: needinfo?(sofiaism)
Unfortunately, Nightly v36.0a1 (2014-11-17) crashed within the first few minutes:

https://crash-stats.mozilla.com/report/index/6083ce72-a18f-4bf6-8476-25b8b2141118
Flags: needinfo?(sofiaism)
(In reply to iSofia from comment #36)
> Unfortunately, Nightly v36.0a1 (2014-11-17) crashed within the first few
> minutes:
> 
> https://crash-stats.mozilla.com/report/index/6083ce72-a18f-4bf6-8476-
> 25b8b2141118

Could you kindly update your video driver to version 3958 and try again: https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=24329
(In reply to iSofia from comment #36)
> Unfortunately, Nightly v36.0a1 (2014-11-17) crashed within the first few
> minutes:
> 
> https://crash-stats.mozilla.com/report/index/6083ce72-a18f-4bf6-8476-
> 25b8b2141118

Actually if you set the media.mediasource.enabled pref to false that should avoid this crash. Try again with that pref set.
(In reply to Jeff Muizelaar [:jrmuizel] from comment #38)
> Actually if you set the media.mediasource.enabled pref to false that should
> avoid this crash. Try again with that pref set.

The media.mediasource.enabled pref was set to false but it crashed again - and this time no crash report.

Windows error message indicated a black screen and some memory read error (sorry, I didn't catch them), and all open apps either crashed or were closed by Windows. Nightly had to be forced closed - no black screen - the top right quadrant of the screen was magnified to fill the whole screen, sort of zoomed.
(In reply to Jeff Muizelaar [:jrmuizel] from comment #40)
> Can you try with this build:
> http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/mozilla-beta-
> win32/1416353364/

Running Nighly 34.0 for about half an hour now, and so far, so good. But that seems like an older 32-bit build though.

Will let it run a little longer and update the progress.
Flags: needinfo?(sofiaism)
Nighly 34.0 (32-bit) seems to be pretty stable, based on the same usage as the previous builds. One solid hour and no issues.
Nighly 34.0 (32-bit) ran over six hours today, with continuous video streaming on YouTube and various other multi-tab browsing without missing a beat. These add-ons are also installed:

1. New Tab Homepage v0.4.3
2. Adblock Plus v2.6.6

Can we expect the same stability for the 64-bit version soon?
(In reply to iSofia from comment #43)
> Nighly 34.0 (32-bit) ran over six hours today, with continuous video
> streaming on YouTube and various other multi-tab browsing without missing a
> beat. These add-ons are also installed:
> 
> 1. New Tab Homepage v0.4.3
> 2. Adblock Plus v2.6.6
> 
> Can we expect the same stability for the 64-bit version soon?

Yes.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
I don't know why this bug has been hijacked by the crashing issues of the user iSofia.

The original bug was about blacknees appearing after tens minutes or hours of browsing, no crash was involved...
Hey Loic. I'm not sure either. But I figure jrmuizel saw some evidence of connection. I really appreciated your work connecting this with the forum reports. But the various "black screen" bugs have been pretty tangled up and hard to reproduce. Here it seems that isofia ran into the same issue as the OP on 33.1. Then was asked to try Nightly, which was super crashy, unrelated to the original bug. 

Are you still seeing reports of black screen issues on 8.1? Since I'm not seeing any actual reports of the original problem on 34, I'm marking 34 as unaffected for now .
(In reply to Loic from comment #5)
> We have 2 reports about this issue on the French board: 
> http://forums.mozfr.org/viewtopic.php?f=5&t=121096

Both users said it was fixed on their side (probably after FF34).
Flags: needinfo?(epinal99-bugzilla2)
Attached image ff34.0.5
I just ran into this bug again on different setup with FF 34.0.5.
Laptop is Dell Inspiron 15R running Windows 8.1 x64.
Below is about graphics.

Graphics
--------
Adapter Description: Intel(R) HD Graphics 3000
Adapter Description (GPU #2): NVIDIA GeForce GT 525M
Adapter Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32
Adapter Drivers (GPU #2): nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM: Unknown
Adapter RAM (GPU #2): 1024
Device ID: 0x0116
Device ID (GPU #2): 0x0df5
Direct2D Enabled: true
DirectWrite Enabled: true (6.3.9600.17111)
Driver Date: 3-20-2014
Driver Date (GPU #2): 9-13-2014
Driver Version: 9.17.10.3517
Driver Version (GPU #2): 9.18.13.4411
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 04ca1028
Subsys ID (GPU #2): 04ca1028
Vendor ID: 0x8086
Vendor ID (GPU #2): 0x10de
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
saurabh, could you file a new bug report, please.
I have another report about your issue, with a white screen.
Hello everyone.
Same issue here, on Firefox 35.0 (no upgrade available at the time of the post).
Below is the autput of about:support regarding the video cards.
Aslo, I use adblocker (latest).


Grafică
Accelerare GPU Windows	1/1 Direct3D 11 (OMTC)
Dată driver	9-29-2014
Dată driver (GPU #2)	11-20-2014
Descriere adaptor (GPU #2) 	AMD Radeon HD 8500M
Descrierea adaptorului	Intel(R) HD Graphics Family
Direct2D activat	true
DirectWrite activat	true (6.3.9600.17111)
Drivere adaptor (GPU #2)	aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Drivere pentru adaptor	igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
GPU #2 activ	false
ID dispozitiv	0x0a16
ID dispozitiv (GPU #2)	0x666f
ID furnizor	0x8086
ID vânzător (GPU #2) 	0x1002
Motor de afișare WebGL	Google Inc. -- ANGLE (Intel(R) HD Graphics Family Direct3D9Ex vs_3_0 ps_3_0)
RAM adaptor (GPU #2)	2048
RAM pentru adaptor	Unknown
Subsys ID	381517aa
Subsys ID (GPU #2)	0000000c
Versiune driver	10.18.10.3960
Versiune driver (GPU #2)	14.501.1003.0
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0



Additional sysyem info:
Lenovo B50-70 with Windows 8.1
Intel HD graphics 4400 with ATI radeon R230
Was playing a video on stirileprotv.ro when the black window came up.
I'm not sure if it's related, but I started experiencing this after changing layers.offmainthreadcomposition.enabled to false a few days ago as a workaround to bug 1065463.

I'm using youtube's html5 player, and it doesn't have to be the active tab for the black content to occur. Using Firefox 35.0.1

Graphics
Adapter Description	Intel(R) HD Graphics 4400
Adapter Drivers	igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
Adapter RAM	Unknown
Device ID	0x041e
Direct2D Enabled	true
DirectWrite Enabled	true (6.2.9200.16571)
Driver Date	7-9-2013
Driver Version	9.18.10.3234
GPU #2 Active	false
GPU Accelerated Windows	1/1 Direct3D 10
Subsys ID	06121028
Vendor ID	0x8086
WebGL Renderer	Google Inc. -- ANGLE (Intel(R) HD Graphics 4400 Direct3D9Ex vs_3_0 ps_3_0)
windowLayerManagerRemote	false
AzureCanvasBackend	direct2d
AzureContentBackend	direct2d
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
I am encountering this issue in FF 51.0.1 on Windows 8.1
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: