If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

[disabled e10s] Graphical glitch during animation

NEW
Unassigned

Status

()

Core
Graphics: Layers
--
trivial
3 years ago
a year ago

People

(Reporter: Alice0775 White, Unassigned)

Tracking

({regression})

34 Branch
x86_64
All
regression
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(e10s-, firefox36 wontfix, firefox37 wontfix, firefox38 wontfix, firefox39 wontfix, firefox40 wontfix, firefox41 wontfix, firefox42 wontfix, firefox43 wontfix, firefox44 wontfix, firefox45 wontfix, firefox46 wontfix, firefox47 wontfix, firefox48 wontfix, firefox49 wontfix, firefox-esr31 unaffected, firefox-esr38 wontfix, firefox-esr45 ?, firefox50 fix-optional)

Details

(Whiteboard: [gfx-noted])

(Reporter)

Description

3 years ago
+++ This bug was initially created as a clone of Bug #1124543 +++

Bug 1124543 does not fix the graphical glitch

Steps to reproduce:
1. Extract attachment 8552868 [details]
2. Open index.html

Actual results:
See attached screenshot See attachment 8552867 [details]

Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=2a61df4eaa2d&tochange=24ba8274ed60

In local build(win32 non pgo)
Last Good: 2a61df4eaa2d
First Bad: 823227372483

Regressed by 823227372483	Bas Schouten — Bug 1107297: Only recomposite the damaged rect with D3D11. r=jrmuizel
Flags: needinfo?(bas)
Whiteboard: [gfx-noted]
status-firefox40: --- → affected
(Reporter)

Updated

2 years ago
status-firefox41: --- → affected
status-firefox42: --- → affected
(Reporter)

Updated

2 years ago
status-firefox36: affected → wontfix
status-firefox37: affected → wontfix
status-firefox38: affected → wontfix
status-firefox39: affected → wontfix
status-firefox40: affected → wontfix
status-firefox41: affected → wontfix
status-firefox42: affected → wontfix
status-firefox43: --- → wontfix
status-firefox44: --- → affected
status-firefox45: --- → affected
status-firefox46: --- → affected
status-firefox-esr38: ? → wontfix
status-firefox-esr45: --- → ?
Summary: Graphical glitch during animation → [disabled e10s] Graphical glitch during animation

Updated

2 years ago
tracking-e10s: --- → -

Updated

2 years ago
status-firefox44: affected → wontfix
status-firefox45: affected → wontfix
status-firefox46: affected → wontfix
status-firefox47: --- → wontfix
status-firefox48: --- → affected
Flags: needinfo?(bas) → needinfo?(milan)
This works for me in the latest nightly on Windows 7, D2D1.1/D3D11.  Alice, do you still see this problem?
Flags: needinfo?(alice0775)
Flags: needinfo?(milan)
(Reporter)

Comment 2

2 years ago
I can still reproduce the problem on Latest Nightly[1]

[1]
https://hg.mozilla.org/mozilla-central/rev/a66bf0a800f3d859b4bd2ceebc57b2e3fa6544d8
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0 ID:20160329030246

Application Basics
------------------

Name: Firefox
Version: 48.0a1
Build ID: 20160329030246
Update Channel: nightly
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
OS: Windows_NT 6.1 x86
Multiprocess Windows: 0/1 (Disabled)
Safe Mode: false

Crash Reports for the Last 3 Days
---------------------------------

Report ID: bp-7a7ad575-6d6a-4bdd-ab3c-96f762160328
Submitted: 2 days ago

All Crash Reports (including 8 pending crashes in the given time range)

Extensions
----------

Name: Firefox Hello Beta
Version: 1.2.2
Enabled: true
ID: loop@mozilla.org

Name: Multi-process staged rollout
Version: 1.0
Enabled: true
ID: e10srollout@mozilla.org

Name: Pocket
Version: 1.0
Enabled: true
ID: firefox@getpocket.com

Graphics
--------

Adapter Description: AMD Radeon HD 6450
Adapter Drivers: aticfx64 aticfx64 aticfx64 aticfx32 aticfx32 aticfx32 atiumd64 atidxx64 atidxx64 atiumdag atidxx32 atidxx32 atiumdva atiumd6a atitmm64
Adapter RAM: 1024
Asynchronous Pan/Zoom: none
ClearType Parameters: Gamma: 2200 Pixel Structure: R ClearType Level: 100 Enhanced Contrast: 300
Device ID: 0x6779
Direct2D Enabled: true
DirectWrite Enabled: true (6.2.9200.17568)
Driver Date: 7-28-2015
Driver Version: 15.200.1062.1003
GPU #2 Active: false
GPU Accelerated Windows: 1/1 Direct3D 11 (OMTC)
Subsys ID: 23111787
Supports Hardware H264 Decoding: Yes; Using D3D9 API
Vendor ID: 0x1002
WebGL Renderer: Google Inc. -- ANGLE (AMD Radeon HD 6450 Direct3D11 vs_5_0 ps_5_0)
windowLayerManagerRemote: true
AzureCanvasAccelerated: 0
AzureCanvasBackend: direct2d 1.1
AzureContentBackend: direct2d 1.1
AzureFallbackCanvasBackend: cairo

Important Modified Preferences
------------------------------

browser.cache.disk.capacity: 1048576
browser.cache.disk.filesystem_reported: 1
browser.cache.disk.smart_size.first_run: false
browser.cache.frecency_experiment: 4
browser.download.importedFromSqlite: true
browser.places.smartBookmarksVersion: 7
browser.sessionstore.upgradeBackup.latestBuildID: 20160329030246
browser.startup.homepage_override.buildID: 20160329030246
browser.startup.homepage_override.mstone: 48.0a1
browser.tabs.remote.autostart.2: false
dom.apps.reset-permissions: true
extensions.lastAppVersion: 48.0a1
gfx.direct3d.last_used_feature_level_idx: 0
media.hardware-video-decoding.failed: false
network.cookie.prefsMigrated: true
places.history.expiration.transient_current_max_pages: 104858
plugin.disable_full_page_plugin_for_types: application/pdf
plugin.importedState: true
privacy.sanitize.migrateFx3Prefs: true
security.sandbox.content.tempDirSuffix: {bde71a43-b805-4db7-87eb-5406e675e310}

Important Locked Preferences
----------------------------

JavaScript
----------

Incremental GC: true

Accessibility
-------------

Activated: false
Prevent Accessibility: 0

Library Versions
----------------

NSPR
Expected minimum version: 4.12
Version in use: 4.12

NSS
Expected minimum version: 3.23 Basic ECC
Version in use: 3.23 Basic ECC

NSSSMIME
Expected minimum version: 3.23 Basic ECC
Version in use: 3.23 Basic ECC

NSSSSL
Expected minimum version: 3.23 Basic ECC
Version in use: 3.23 Basic ECC

NSSUTIL
Expected minimum version: 3.23
Version in use: 3.23

Experimental Features
---------------------
Flags: needinfo?(alice0775)
(Reporter)

Updated

2 years ago
Severity: normal → trivial
For the original bug, we concluded (bug 1124543 comment 4) "...layout incorrectly reporting the damaged rect to the layer manager...", and some of it got fixed.  Bas, is there a good way to confirm this is still the case with the remaining issue?  For example, if that was the case, would you expect to see the same problem without hardware acceleration?
Flags: needinfo?(bas)
(In reply to Milan Sreckovic [:milan] from comment #3)
> For the original bug, we concluded (bug 1124543 comment 4) "...layout
> incorrectly reporting the damaged rect to the layer manager...", and some of
> it got fixed.  Bas, is there a good way to confirm this is still the case
> with the remaining issue?  For example, if that was the case, would you
> expect to see the same problem without hardware acceleration?

Not really actually. Without hardware acceleration I believe GDI will automatically 'clip' to the actual damaged area which could lead to significantly different symptoms.
Flags: needinfo?(bas)

Comment 5

a year ago
I am experiencing this bug in Firefox 47.0 on GNU/Linux. I'm not sure whether to report my issues as another bug, or simply comment here. I figure I will post here first since it doesn't hurt.

I'm experiencing the exact same effect as what is shown in the attached screenshot from comment #0, but I am also getting these weird graphical glitches with the animation that plays when downloads finish and with the red loading bar at the top of YouTube.

Oddly, though, the specific graphical glitch shown in comment #0 doesn't happen in fullscreen.
Not likely to be the same problem, given that the above was D2D specific, but anything is possible.  Could you get a regression range using mozregression tool and let us know what you get?  In this bug is fine, we can split them off easily enough.

Comment 7

a year ago
Okay, so I tried getting a regression range using mozregression for a couple of versions back, but I didn't get my specific issue to occur in any of them. However, while the bug described in comment #0 doesn't occur in any of the >= 40 versions, it does occur in all of them when using a non-e10s window.

For my more specific issues, I can confirm that the issue seems to have first occurred in Firefox 47.0. I have tested many of the official releases, and none of the earlier releases before 47 have the issue.

I am looking at finding a way to reliably reproduce it.
status-firefox48: affected → wontfix
status-firefox49: --- → wontfix
status-firefox50: --- → fix-optional
You need to log in before you can comment on or make changes to this bug.