Stop to trigger device reset in gfx/SanityTest if WebRender is used

RESOLVED FIXED in Firefox 65

Status

()

P2
normal
RESOLVED FIXED
a month ago
21 days ago

People

(Reporter: sotaro, Assigned: sotaro)

Tracking

unspecified
mozilla65
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox65 fixed)

Details

Attachments

(1 attachment)

(Assignee)

Description

a month ago
It is not necessary to call nsDOMWindowUtils::TriggerDeviceReset() in  gfx/SanityTest if WebRender is used.

TriggerDeviceReset() is called for disabling advanced layer, but the advanced layer is not used when WebRender is used.

https://dxr.mozilla.org/mozilla-central/source/toolkit/components/gfx/SanityTest.js#145
(Assignee)

Updated

a month ago
Assignee: nobody → sotaro.ikeda.g
(Assignee)

Updated

a month ago
Blocks: 1497910
(Assignee)

Comment 1

a month ago
Created attachment 9017097 [details] [diff] [review]
patch - Stop to trigger device reset in gfx/SanityTest if WebRender is used
(Assignee)

Updated

29 days ago
Attachment #9017097 - Flags: review?(matt.woodrow)
(Assignee)

Updated

29 days ago
Summary: Do not trigger device reset in gfx/SanityTest if WebRender is used → Stop to trigger device reset in gfx/SanityTest if WebRender is used
(Assignee)

Updated

29 days ago
Attachment #9017097 - Attachment description: patch - Do not trigger device reset in gfx/SanityTest if WebRender is used → patch - Stop to trigger device reset in gfx/SanityTest if WebRender is used
Attachment #9017097 - Flags: review?(matt.woodrow) → review+
Priority: -- → P2

Comment 3

22 days ago
Pushed by sikeda@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/99bd9a8c917c
Stop to trigger device reset in gfx/SanityTest if WebRender is used r=mattwoodrow

Comment 4

22 days ago
bugherder
https://hg.mozilla.org/mozilla-central/rev/99bd9a8c917c
Status: NEW → RESOLVED
Last Resolved: 22 days ago
status-firefox65: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla65
(Assignee)

Updated

21 days ago
Blocks: 1496825
You need to log in before you can comment on or make changes to this bug.