Closed
Bug 1172315
Opened 9 years ago
Closed 9 years ago
background artifacts rendering horizontal ~15px lines based on elements on page
Categories
(Core :: Graphics, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: skaviouz, Unassigned, NeedInfo)
References
Details
(Whiteboard: gfx-noted)
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0 Build ID: 20150525141253 Steps to reproduce: https://octobercms.com/plugins/new?sort=last-updated&page=3#list just scroll up and down or go to another page Expected results: see https://github.com/octobercms/october/issues/1193 https://camo.githubusercontent.com/2ee12ba27381a9c9d8f69e33d3c70fc2f0d52ded/687474703a2f2f692e696d6775722e636f6d2f4f65613544726a2e706e67 possible related: https://bugzilla.mozilla.org/show_bug.cgi?id=305224 possibly related to graphics card windows 10_10041 firefox 38.0.5 But I havn't seen this issue on other websites. I can't reproduce this bug in IE, so it must be a firefox issue.
additional example: http://i.imgur.com/B9vUqzE.png while scrolling up and down, the artifact is momentarily fixed then distorts again after settling. oh tab switching, the distortion is removed entirely. This bug is hard to reproduce consistently.
http://i.imgur.com/5w3vt1i.png It seems to be the graphics renderer, because notice how the distortions follow a certain pattern. Look at the placement of the artifacts, and how they form in the pictures, and around text; as if avoiding something.
Comment 3•9 years ago
|
||
Please type about:support into the location bar, then press Enter. Click the “Copy text to clipboard” button, then paste the clipboard contents in a comment here.
Component: Untriaged → Graphics
OS: Unspecified → Windows 10
Product: Firefox → Core
Hardware: Unspecified → x86_64
about:support pastebin http://pastebin.com/iT00ddcG
Comment 5•9 years ago
|
||
Thank you for the update. Can you reproduce the issue when you do the following? 1. Paste the following into the location bar, then press Enter. about:config?filter=direct2d 2. Click the “I'll be careful, I promise!” button to bypass the warning. 3. Double-click gfx.direct2d.use1_1 to set its value to false 4. Double-click gfx.content.azure.backends and set its value to direct2d,cairo 5. Double-click gfx.canvas.azure.backends and set its value to direct2d,cairo 6. Restart Firefox. If that makes no difference, what about this? 1. Paste the following into the location bar, then press Enter. about:config?filter=direct2d 2. Right-click each preference that has the status User Set, then choose Reset. 3. Paste the following into the location bar, then press Enter. about:config?filter=layers.offmainthreadcomposition.enabled 4. Double-click layers.offmainthreadcomposition.enabled to set its value to false. 5. Restart Firefox.
Comment 6•9 years ago
|
||
(In reply to Gingerbread Man from comment #5) > Thank you for the update. > > Can you reproduce the issue when you do the following? > 1. Paste the following into the location bar, then press Enter. > about:config?filter=direct2d > 2. Click the “I'll be careful, I promise!” button to bypass the warning. > 3. Double-click gfx.direct2d.use1_1 to set its value to false > 4. Double-click gfx.content.azure.backends and set its value to > direct2d,cairo > 5. Double-click gfx.canvas.azure.backends and set its value to direct2d,cairo > 6. Restart Firefox. > > If that makes no difference, what about this? > 1. Paste the following into the location bar, then press Enter. > about:config?filter=direct2d > 2. Right-click each preference that has the status User Set, then choose > Reset. > 3. Paste the following into the location bar, then press Enter. > about:config?filter=layers.offmainthreadcomposition.enabled > 4. Double-click layers.offmainthreadcomposition.enabled to set its value to > false. > 5. Restart Firefox. Did you try these steps? Is this still an issue on more recent versions of Windows 10 (we're at build 10130 by now) ?
Flags: needinfo?(skaviouz)
Comment 7•9 years ago
|
||
The page in comment 0 works for me, I don't see glitches on my Surface Pro. This was likely a graphics driver bug, guessing from the screenshot. And presumably fixed in the couple of months of Windows 10 prerelease changes since this was filed. Please reopen if you can reproduce on the release version of Windows 10 with updated drivers!
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•