Closed Bug 1298009 Opened 9 years ago Closed 2 months ago

page all black (or mostly black)

Categories

(Core :: Graphics, defect, P3)

51 Branch
Unspecified
Windows
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox57 --- fix-optional

People

(Reporter: wsmwk, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

Attachments

(3 files)

recently I've seen a few examples of newly opened pages all black. So far I think the only cases have been BMO pages. I found that error console shows "container is null" content.js. Reload doesn't help, and each time kicks a new "container is null". 20160816030459 nightly build Yesterday (Wednesday) I installed Bugzilla Socorro Lens add-on. But the problem may have started before that. I've had all add-ons forever, except "lens". Only TST and font size addons update frequently. About sessionstore 0.32.1-signed.1-signed true aboutsessionstore@dt Bugzilla Socorro Lens 0.3 true bugzilla-socorro-lens@ashughes.com CopyAllUrls 0.9.2 true {960BE052-4847-422b-9AD6-8631D3D0A607} Flashblock 1.5.20 true {3d7eb24f-2740-49df-8937-200b1cc08f8a} FlyWeb 1.0.0 true flyweb@mozilla.org HTTPS-Everywhere 5.2.1 true https-everywhere@eff.org Multi-process staged rollout 1.0 true e10srollout@mozilla.org Nightly Tester Tools 3.7.1-signed.1-signed true {8620c15f-30dc-4dba-a131-7c5d20cf4a29} Pocket 1.0.4 true firefox@getpocket.com Restartless Restart 9.1-signed.1-signed true restartless.restart@erikvold.com Revert Keyword Column 1.2.1-signed.1-signed true revertKeywordColumn@alice Tabhunter 1.0.29 true tabhunter@ericpromislow.com Theme Font & Size Changer 48.3 true {f69e22c7-bc50-414a-9269-0f5c344cd94c} Tree Style Tab 0.17.2016082100a014627 true treestyletab@piro.sakura.ne.jp ViewAbout 2.1.2 true viewabout@rumblingedge.com Web Compat 1.0 true webcompat@mozilla.org
e10s is enabled. loading the URL in a different tab works. loading a different, non BMO URL in the SAME tab fails black - but does not kick a "container is null". And loading a BMO URL in any tab kicks the same js error, so it is not a symptom of the black screen. Graphics -------- Features Compositing: Direct3D 11 Asynchronous Pan/Zoom: wheel input enabled; touch input enabled WebGL Renderer: Google Inc. -- ANGLE (Intel(R) HD Graphics 3000 Direct3D11 vs_4_1 ps_4_1) WebGL2 Renderer: WebGL creation failed: * Refused to create native OpenGL context because of blacklist entry: WEBGL_NATIVE_GL_OLD_INTEL * Exhausted GL driver options. Hardware H264 Decoding: No; Hardware video decoding disabled or blacklisted Audio Backend: wasapi Direct2D: true DirectWrite: true (6.2.9200.17568) GPU #1 Active: Yes Description: Intel(R) HD Graphics 3000 Vendor ID: 0x8086 Device ID: 0x0126 Driver Version: 9.17.10.4229 Driver Date: 5-26-2015 Drivers: igdumd64 igd10umd64 igd10umd64 igdumd32 igd10umd32 igd10umd32 Subsys ID: 21d117aa RAM: Unknown GPU #2 Active: No Description: NVIDIA Quadro 1000M Vendor ID: 0x10de Device ID: 0x0dfa Driver Version: 10.18.13.5382 Driver Date: 8-7-2015 Drivers: nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um Subsys ID: 21d117aa RAM: 2048 Diagnostics ClearType Parameters: Gamma: 2.2 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 400 AzureCanvasAccelerated: 0 AzureCanvasBackend: direct2d 1.1 AzureContentBackend: direct2d 1.1 AzureFallbackCanvasBackend: cairo ClearType Parameters: Gamma: 2.2 Pixel Structure: RGB ClearType Level: 100 Enhanced Contrast: 400 failures: CP+[GFX1-]: Detected rendering device reset on refresh: 2 Decision Log HW_COMPOSITING: force_enabled by user: Force-enabled by pref D3D9_COMPOSITING: force_enabled by user: Hardware compositing is force-enabled Failure Log (#0): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9298): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9299): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9300): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9301): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9302): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9303): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9304): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9305): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9306): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9307): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9308): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9309): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9310): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9311): CP+[GFX1-]: Detected rendering device reset on refresh: 2 (#9312): CP+[GFX1-]: Detected rendering device reset on refresh: 2 Important Modified Preferences ------------------------------ accessibility.typeaheadfind: true accessibility.typeaheadfind.flashBar: 0 browser.cache.disk.capacity: 460800 browser.cache.disk.filesystem_reported: 1 browser.cache.disk.hashstats_reported: 1 browser.cache.disk.smart_size_cached_value: 327680 browser.cache.disk.smart_size.enabled: false browser.cache.disk.smart_size.first_run: false browser.cache.disk.smart_size.use_old_max: false browser.cache.frecency_experiment: 4 browser.cache.use_new_backend: 1 browser.download.importedFromSqlite: true browser.download.manager.alertOnEXEOpen: false browser.fixup.domainwhitelist.192.168.1.1: true browser.link.open_newwindow.restriction: 0 browser.link.open_newwindow.restriction.backup: 2 browser.places.smartBookmarksVersion: 8 browser.privatebrowsing.dont_prompt_on_enter: true browser.search.useDBForOrder: false browser.sessionstore.interval: 90000 browser.sessionstore.max_tabs_undo: 5 browser.sessionstore.restore_on_demand: false browser.sessionstore.upgradeBackup.latestBuildID: 20160816030459 browser.startup.homepage: about:blank browser.startup.homepage_override.buildID: 20160816030459 browser.startup.homepage_override.mstone: 51.0a1 browser.tabs.animate: false browser.tabs.crashReporting.email: vseerror@lehigh.edu browser.tabs.crashReporting.emailMe: true browser.tabs.crashReporting.includeURL: true browser.tabs.loadFolderAndReplace: false browser.tabs.onTop: false browser.tabs.remote.force-enable: true browser.tabs.warnOnClose: false browser.urlbar.suggest.searches: true browser.urlbar.userMadeSearchSuggestionsChoice: true browser.zoom.siteSpecific: false dom.apps.lastUpdate.buildID: 20160808002253 dom.apps.lastUpdate.mstone: 49.0 dom.apps.reset-permissions: true dom.icc.enabled: true dom.ipc.plugins.flash.subprocess.crashreporter.enabled: false dom.ipc.processCount: 9 dom.ipc.processes: 9 dom.mozApps.runUpdate: false dom.mozApps.used: true dom.w3c_touch_events.expose: false extensions.checkCompatibility.4.2a: false extensions.checkCompatibility.8.0a: false extensions.checkCompatibility.nightly: false extensions.lastAppVersion: 51.0a1 font.internaluseonly.changed: false font.name.sans-serif.x-western: Arial Black general.autoScroll: false gfx.blacklist.suggested-driver-version: 10.6 gfx.crash-guard.d3d11layers.appVersion: 49.0 gfx.crash-guard.d3d11layers.deviceID: 0x0126 gfx.crash-guard.d3d11layers.driverVersion: 9.17.10.4229 gfx.crash-guard.d3d11layers.feature-d2d: true gfx.crash-guard.d3d11layers.feature-d3d11: true gfx.crash-guard.glcontext.gfx.driver-init.direct3d11-angle: true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle: true gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-d3d11: false gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-force-warp: false gfx.crash-guard.glcontext.gfx.driver-init.webgl-angle-try-d3d11: true gfx.crash-guard.status.d3d11layers: 2 gfx.crash-guard.status.d3d9video: 2 gfx.crash-guard.status.glcontext: 2 gfx.direct3d.last_used_feature_level_idx: 0 gfx.driver-init.appVersion: 42.0a1 gfx.driver-init.deviceID: 0x0126 gfx.driver-init.driverVersion: 9.17.10.4229 gfx.driver-init.feature-d2d: true gfx.driver-init.feature-d3d11: true gfx.driver-init.status: 2 javascript.options.mem.log: true layers.acceleration.force-enabled: true
I just encounted another example. I opened 4 links at github, 2 of the four show mostly black. Attaching screen shot of this compared to a good github issue page, and the BMO page
Component: Untriaged → Graphics
Product: Firefox → Core
Summary: page all black and error console shows "container is null" content.js → page all black (or mostly black)
Attached image FF black page - BMO.png
To start, please do the following: 1) Please make sure all OS and driver updates are installed. 2) Check if this happens on a completely new profile with no changes from the default config 3) Check if this happens with HWA disabled 4) Check if this happens with an older Nightly 5) Check if this happens with the default Windows theme Thanks
Flags: needinfo?(vseerror)
OS: Unspecified → Windows
Whiteboard: [gfx-noted]
Version: Trunk → 51 Branch
I'll start with #1 graphics driver. current nvidia driver is dated 12/2015. Regarding #5, I'm using a non-aero windows theme specifically windows classic, and default Firefox theme. Regarding #4, older nightly, I've been on 2016-08-16 for 8 days, with 7 days of no problems. (was on 2016-08-09 prior to that) In these situations - I can never decide whether I want a problem to be reproducible, or simply go away on its own :)
Flags: needinfo?(vseerror)
Not seen a black page for a day, but now I'm seeing bug 1298631 and bug 1298624
Flags: needinfo?(vseerror)
seeing this again today, after a long time of not seeing it 51.0a1 (2016-09-14) (64-bit)
See Also: → 1298631
Flags: needinfo?(vseerror)
Severity: normal → S3

Not seen this recently.

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: