Closed
Bug 1468873
Opened 6 years ago
Closed 6 years ago
fishbowl causes flicker
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: sotaro, Assigned: sotaro)
References
()
Details
testdrive-archive.azurewebsites.net/performance/fishbowl showed flickering on my Win10 PC with nightly. It did not saw it in the past.
Assignee | ||
Updated•6 years ago
|
OS: Unspecified → Windows
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Comment 1•6 years ago
|
||
I'm unable to reproduce this problem on Win10 with Nvidia GTX 1060.
But after I was reading in another tab and switched back to Fish Bowl's tab, it had a red background for a fraction of a second.
Then I noticed that if I click on "Trigger Device Reset" on about:support I see the blue water as background for the whole page. If I click on "Terminate GPU Process" the whole page is red. Both can be fixed with F5. Without WebRender, the page has the buggy water background in both cases.
Assignee | ||
Comment 2•6 years ago
|
||
Hmm, I just updated nightly, then I could not reproduce the problem.
Assignee | ||
Comment 3•6 years ago
|
||
(In reply to Jan Andre Ikenmeyer [:darkspirit] from comment #1)
> I'm unable to reproduce this problem on Win10 with Nvidia GTX 1060.
>
> But after I was reading in another tab and switched back to Fish Bowl's tab,
> it had a red background for a fraction of a second.
> Then I noticed that if I click on "Trigger Device Reset" on about:support I
> see the blue water as background for the whole page. If I click on
> "Terminate GPU Process" the whole page is red. Both can be fixed with F5.
> Without WebRender, the page has the buggy water background in both cases.
Yea, the problem seems to related to "Device Reset" and "Terminate GPU Process".
Assignee | ||
Comment 4•6 years ago
|
||
The following STR seems to reproduce the flickering for me.
[1] Start Firefox
[2] Move to about:support and click on "Trigger Device Reset"
[3] Move to https://testdrive-archive.azurewebsites.net/performance/fishbowl/
If the problem does not happen continue [2][3].
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 5•6 years ago
|
||
Part of the problem might be addressed by Bug 1469480.
Assignee | ||
Comment 6•6 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #4)
> The following STR seems to reproduce the flickering for me.
>
> [1] Start Firefox
> [2] Move to about:support and click on "Trigger Device Reset"
> [3] Move to https://testdrive-archive.azurewebsites.net/performance/fishbowl/
>
> If the problem does not happen continue [2][3].
The following STR is valid on my Win10 PC(P50).
[1] Start Firefox
[2] Move to about:support and click on "Ternimate GPU Process"
[3] Move to https://testdrive-archive.azurewebsites.net/performance/fishbowl/
Updated•6 years ago
|
Blocks: stage-wr-nightly
Priority: -- → P2
Assignee | ||
Comment 7•6 years ago
|
||
The flicker actually caused by the video of water.
https://testdrive-archive.azurewebsites.net/performance/fishbowl/video/water.mp4
Assignee | ||
Comment 8•6 years ago
|
||
When the problem happned, there were the following error messages.
> GP+[GFX1]: RenderDXGIYCbCrTextureHostOGL AcquireSync timeout, hr=0x80070057
Assignee | ||
Comment 9•6 years ago
|
||
The problem might be a driver specific problem. I did not see the problem on my Win10 PC with NVIDIA GeForce GTX 960.
Assignee | ||
Comment 10•6 years ago
|
||
When the problem happened, IMFYCbCrImage was used in content process to hold video data.
Assignee | ||
Comment 11•6 years ago
|
||
IMFYCbCrImage usage might cause the problem. IMFYCbCrImage does not recycle ID3D11Texture2D and create ID3D11Texture2D just before forwarding to GPU process.
Assignee | ||
Comment 12•6 years ago
|
||
Assignee | ||
Comment 13•6 years ago
|
||
Confirmed that the issue was addressed on latest nightly with Bug 1470386.
Assignee | ||
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•