Closed
Bug 1366915
Opened 8 years ago
Closed 8 years ago
Change async pipeline id allocation
Categories
(Core :: Graphics: WebRender, enhancement)
Core
Graphics: WebRender
Tracking
()
RESOLVED
FIXED
mozilla55
Tracking | Status | |
---|---|---|
firefox55 | --- | fixed |
People
(Reporter: sotaro, Assigned: sotaro)
References
Details
Attachments
(2 files, 1 obsolete file)
11.69 KB,
patch
|
nical
:
review+
|
Details | Diff | Splinter Review |
7.96 KB,
patch
|
sotaro
:
review+
|
Details | Diff | Splinter Review |
By Bug 1345054 Comment 19, it became clear that current async pipeline id allocation caused reftest failures.
pipeline id allocation often did not happen before reftest.
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → sotaro.ikeda.g
Assignee | ||
Comment 1•8 years ago
|
||
There seems 3 ways to address the problem.
[1] Share id name space between layers id(pipeline id) and external image id
[2] Split layers id and pipeline id
[3] Wait async pipeline id allocation before reftest.
[3] seems not good approach. [2] was already rejected by Bug 1358014 Comment 10. Then this bug is going to seek [3].
Assignee | ||
Comment 2•8 years ago
|
||
Assignee | ||
Comment 3•8 years ago
|
||
Assignee | ||
Updated•8 years ago
|
Attachment #8870246 -
Flags: review?(bugmail)
Assignee | ||
Updated•8 years ago
|
Attachment #8870247 -
Flags: review?(bugmail)
Comment 4•8 years ago
|
||
(In reply to Sotaro Ikeda [:sotaro] from comment #1)
> There seems 3 ways to address the problem.
> [1] Share id name space between layers id(pipeline id) and external image id
> [2] Split layers id and pipeline id
> [3] Wait async pipeline id allocation before reftest.
>
> [3] seems not good approach. [2] was already rejected by Bug 1358014 Comment
> 10. Then this bug is going to seek [3].
I don't understand this comment. Specially the last line, you say [3] is not a good approach and then you say you're going to do [3]. Did you mean [1] is not a good approach? I also don't really understand the problem that you're trying to solve here - all I can figure out is that the async-ness of the pipeline id allocation is somehow causing a problem but I don't understand how or why. Maybe nical would be a better reviewer for this.
Assignee | ||
Updated•8 years ago
|
Attachment #8870246 -
Flags: review?(bugmail)
Assignee | ||
Updated•8 years ago
|
Attachment #8870247 -
Flags: review?(bugmail)
Assignee | ||
Comment 5•8 years ago
|
||
Thanks, I am going to ask nical for a review.
Assignee | ||
Updated•8 years ago
|
Attachment #8870246 -
Flags: review?(nical.bugzilla)
Assignee | ||
Updated•8 years ago
|
Attachment #8870247 -
Flags: review?(nical.bugzilla)
Updated•8 years ago
|
Attachment #8870247 -
Flags: review?(nical.bugzilla) → review+
Updated•8 years ago
|
Attachment #8870246 -
Flags: review?(nical.bugzilla) → review+
Assignee | ||
Updated•8 years ago
|
Attachment #8872477 -
Flags: review+
Pushed by sikeda@mozilla.com:
https://hg.mozilla.org/projects/graphics/rev/9fb4a2607ce1
part 1 - Remove pipeline id allocation with IPC MozPromise r=nical
https://hg.mozilla.org/projects/graphics/rev/392436e4adff
part 2 - Make CompositorBridgeChild allocate pipeline id for async image pipeline r=nical
Comment 8•8 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/9fb4a2607ce1
https://hg.mozilla.org/mozilla-central/rev/392436e4adff
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox55:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
You need to log in
before you can comment on or make changes to this bug.
Description
•