Closed Bug 1183534 Opened 9 years ago Closed 9 years ago

Black screen after 10 to 1000 minutes Firefox 39.0

Categories

(Core :: Graphics, defect)

Product:
Core
Component:
Graphics
Version:
39 Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: fopetsys, Unassigned)

References

Details

(Whiteboard: [gfx-noted])

Attachments

(1 file)

about:memory report
240.59 KB, application/gzip
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150630154324 Steps to reproduce: Random web page (re)loading. Can occur on any web page either new or refreshed. Actual results: Black screen which reloading doesn't cure and this applies to any already opened tab/window. Only cure is to shut down Firefox and reload then it can be OK for minutes or hours. Expected results: Normal page (re)load.
Next time this happens, can you check Firefox's memory usage in the task manager? Also, could you go to Help > Troubleshooting Information, and copy/paste the "graphics" section into a comment on this bug?
Flags: needinfo?(fopetsys)
This good enough? ..... Graphics Adapter Description NVIDIA GeForce 7300 GT (Microsoft Corporation - WDDM) Adapter Drivers nvd3dum nvwgf2um Adapter RAM 256 Asynchronous Pan/Zoom none Device ID 0x0393 Direct2D Enabled Blocked for your graphics driver version. Try updating your graphics driver to version 182.65 or newer. DirectWrite Enabled false (6.1.7600.16385) Driver Date 5-14-2009 Driver Version 8.15.11.8593 GPU #2 Active false GPU Accelerated Windows 2/2 Direct3D 11 WARP (OMTC) Subsys ID 04121462 Vendor ID 0x10de WebGL Renderer Blocked for your graphics driver version. Try updating your graphics driver to version 182.65 or newer. windowLayerManagerRemote true AzureCanvasBackend skia AzureContentBackend cairo AzureFallbackCanvasBackend cairo AzureSkiaAccelerated 0 I note the "..updating your graphics driver..." but I live by the mantra, "if it ain't broke, don't fix it". Unless, of course, you advise doing so :o)
Flags: needinfo?(fopetsys)
It is possible your graphics driver is causing the blackness (in which case updating it might help), but it is equally possible Firefox is running out of usable memory - hence my first question. Your graphics driver is now 6+ years old. I am not an expert on graphics drivers, but updating might help.
AS to memory, I have 4GB installed and memory usage in Task Manager says 1.68GB used. Firefox is taking nearly 1GB! I'll watch for what you suggest.
I (re)checked the video driver. Windows says it is the latest available. Firefox says to upgrade to v 182.65, a version number completely different to the one installed.
Yet another odd effect. Youtube: https://www.youtube.com/watch?v=eLSZyv0bFRE Movie video freezes but sound continues normally. Video sometimes catches up but eventually freezes. Firefox using 1.4GB, reload Firefox with all windows and tabs Firefox using 1.1GB memory.
Milan/Nicholas, any idea how to take this further?
Flags: needinfo?(n.nethercote)
Flags: needinfo?(milan)
Yet another odd effect. Youtube: https://www.youtube.com/watch?v=eLSZyv0bFRE Movie video freezes but sound continues normally. Video sometimes catches up but eventually freezes. Firefox using 1.4GB, reload all windows and tabs Firefox using 1.1GB memory.
Sorry. Don't know how the double post occurred. Cannot find a way to delete.
The memory part could be bug 1181753; the not drawing could be bug 1183391, except for the hibernation part. When this happens, does resizing the window (temporarily, or in parts) fix the problem?
Flags: needinfo?(milan)
Whiteboard: [gfx-noted]
about:memory contents might be helpful. Instructions on how to gather them are at the top of https://developer.mozilla.org/en-US/docs/Mozilla/Performance/about:memory.
Flags: needinfo?(n.nethercote)
Got that. I'll try both suggestions when it happens next though sometimes Firefox locks up so the memory option may not be available.
Just had one experience of the problem. Yahoo mail page only part loaded with black areas around inbox messages. Reducing screen size did clear the problem but it took a few seconds. Subsequently other page reloads pixellated (large pixel area) for perhaps 30 seconds. The problem has not recurred yet. I ran about:memory and have a ..gz file but how to attach? The about:memory link suggests it can be included in Bugzilla?
Oh! Checking Task Manager memory usage Firefox usage has dropped from 1.3GB to 680MB!
(In reply to Peter from comment #13) > Just had one experience of the problem. Yahoo mail page only part loaded > with black areas around inbox messages. > Reducing screen size did clear the problem but it took a few seconds. > Subsequently other page reloads pixellated (large pixel area) for perhaps 30 > seconds. The problem has not recurred yet. > > I ran about:memory and have a ..gz file but how to attach? The about:memory > link suggests it can be included in Bugzilla? Yes, here: https://bugzilla.mozilla.org/attachment.cgi?bugid=1183534&action=enter
Attached file about:memory report —
In the 15+ minutes since I noted memory usage at 608MB, the usage has increased to 1GB. No extra tabs or windows since then.
The memory reports you've attached show very little that's suspicious. If you could get a second set of reports from when the memory is higher then we could get a diff, which would be very helpful. Thank you.
Flags: needinfo?(fopetsys)
Hmmm. Doesn't work this time. Open new tab, OK. Close new tab... Black screen. Check memory usage = 1.5GB Open new tab. Black screen. Click Restore Down icon, Screen reappears. Memory usage 750MB! (memory usage from Task Manager)
The other thing, while we're at it; we will be disabling WARP by default on Windows 7 shortly, and it'd be interesting to see if this problem is reduced or goes away when we do that. You can simulate what that would be like by opening about:config, finding and changing preference layers.d3d11.disable-warp to true and restarting firefox.
Done. WTF is WARP?
Flags: needinfo?(fopetsys)
If you can get two about:memory snapshots from a single session, with one at something like 750 MiB and the other at over 1 GiB, that has a good chance of helping with the diagnosis. I understand it might be tricky and take a few attempts. Thank you for your patience.
Since I disabled WARP the problem has not reappeared. So that's four days without a hitch. Problem cured? So. What is/was WARP?
(In reply to Peter from comment #23) > Since I disabled WARP the problem has not reappeared. > So that's four days without a hitch. > Problem cured? > > So. What is/was WARP? I just googled for "windows WARP" and immediately found these two links: https://en.wikipedia.org/wiki/Windows_Advanced_Rasterization_Platform https://msdn.microsoft.com/en-us/library/windows/desktop/gg615082%28v=vs.85%29.aspx So it's part of the graphics sub-system.
AH! That explains why the problem seems resolved. Thanks for the links. I'd assumed WARP is/was a Mozilla feature, not Windoze. Should remember my forces training, "Don't assume. Check!"
Right - WARP is basically Microsoft's software emulator of the graphics card. It works decently well most of the time, usually with only about a 2x slowdown, but we've been collecting enough reports of strange things happening when Windows 7 and WARP are used in Firefox, so we're going back to not using it for OS versions before Windows 8.
Depends on: 1079504
I'm puzzled, Milan, why would Microsoft want to emulate a graphics card? Firefox works well without the WARP it seems so why complicate the scenario.
That's a good question - in theory, it lets you work around buggy graphics drivers. So, if you have software that needs a particular version of a graphics driver, and the system doesn't have that driver installed, pre-WARP you had two options - don't run, or run without using Direct2d/Direct3d (so, have a fallback path.) Post-WARP, you had a third option - use your Direct2D/Direct3D calls (so, don't have to write a fallback path), just switch to WARP. When it works :)
(In reply to Milan Sreckovic [:milan] from comment #26) > Right - WARP is basically Microsoft's software emulator of the graphics > card. It works decently well most of the time, usually with only about a 2x > slowdown, but we've been collecting enough reports of strange things > happening when Windows 7 and WARP are used in Firefox, so we're going back > to not using it for OS versions before Windows 8. I think you set a dependency on the wrong bug number here?
Flags: needinfo?(milan)
(In reply to :Margaret Leibovic from comment #29) > I think you set a dependency on the wrong bug number here? Right, the old "off by 100,000 error".
Depends on: 1179504
No longer depends on: 1079504
Flags: needinfo?(milan)
Hi Milan, We are cleaning up untriaged items. Please assist us by selecting an appropriate component for this issue. Thanks
Flags: needinfo?(milan)
Component: Untriaged → Graphics
Flags: needinfo?(milan)
Product: Firefox → Core
It is not reproducible. Closing it as works for me. Feel free to reopen the bug if it still reproduces in the latest versions.Thanks
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(fopetsys)
Resolution: --- → WORKSFORME
Flags: needinfo?(fopetsys)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: