Closed Bug 1176734 Opened 9 years ago Closed 2 months ago

Page fails to display correctly

Categories

(Core :: Graphics: Layers, defect)

39 Branch
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: Andrew, Unassigned)

References

()

Details

(Whiteboard: [gfx-noted])

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0
Build ID: 20150604162752

Steps to reproduce:

Open http://www.bloomberg.com/graphics/2015-paul-ford-what-is-code/


Actual results:

The top 1/4 of the page works, but after a while chunks of the page start displaying repeatedly - you hit a piece of the page with animation in it, and suddenly the same three lines appear over and over.

Switching away from the tab and back again fixes this.  I have no idea why.


Expected results:

The text, images, and animations should have displayed correctly (as they do in Chrome, IE, and Firefox when you tab away/back).
I tested with Beta, I'm able to scroll and see the entire webpage.

Could you test:
1) with a fresh profile: https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
2) with HWA disabled (restart Beta to apply): https://support.mozilla.org/en-US/kb/forum-response-disable-hardware-acceleration
Flags: needinfo?(Andrew)
I turned off hardware acceleration, restarted, switched back to the tab, and started scrolling down the page.  Got about halfway down and Firefox crashed.  Submitted a report, restarted the browser, scrolled down the page again, crashed again, submitted a report again.

Not sure how to find auto-submitted reports, sadly.
Flags: needinfo?(Andrew)
Switched to a brand new profile, as per instructions.
Turned off HW Acceleration.
Opened page.
Scrolled down (with scroll wheel)
Crashed at exactly the same point as above.
Submitted report again, in case it gave you any more info to work on.
Do you have any crash reports in the page about:crashes (bp-...)?
You can type about:about, there is a list of all the about pages.
It seems to be related to graphics.

Could you type about:support and paste here the section "graphics", please.
Component: Untriaged → Graphics: Layers
Product: Firefox → Core
Adapter Description	Intel(R) HD Graphics 4600
Adapter Description (GPU #2)	NVIDIA GeForce 825M
Adapter Drivers	igdumdim64 igd10iumd64 igd10iumd64 igdumdim32 igd10iumd32 igd10iumd32
Adapter Drivers (GPU #2)	nvd3dumx,nvwgf2umx,nvwgf2umx nvd3dum,nvwgf2um,nvwgf2um
Adapter RAM	Unknown
Adapter RAM (GPU #2)	1024
Device ID	0x0416
Device ID (GPU #2)	0x1296
Direct2D Enabled	true
DirectWrite Enabled	true (6.3.9600.17795)
Driver Date	11-15-2013
Driver Date (GPU #2)	10-28-2013
Driver Version	10.18.10.3355
Driver Version (GPU #2)	9.18.13.2762
GPU #2 Active	false
GPU Accelerated Windows	1/1 Direct3D 11 (OMTC)
Subsys ID	21091b0a
Subsys ID (GPU #2)	21091b0a
Vendor ID	0x8086
Vendor ID (GPU #2)	0x10de
WebGL Renderer	Google Inc. -- ANGLE (Intel(R) HD Graphics 4600 Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote	true
AzureCanvasBackend	direct2d 1.1
AzureContentBackend	direct2d 1.1
AzureFallbackCanvasBackend	cairo
AzureSkiaAccelerated	0
Two of the three are tagged as "out of memory" problems, but the third one seems to depend on bug 1176024 getting fixed.
Depends on: 1176024
Whiteboard: [gfx-noted]
Severity: normal → S3

Reporter, are you still experiencing this issue?

Flags: needinfo?(Andrew)

All works fine now. Thank you!

Flags: needinfo?(Andrew)

Thanks for following up!

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