Closed Bug 1340067 Opened 9 years ago Closed 9 years ago

Change DPBegin() to async

Categories

(Core :: Graphics: WebRender, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla54

People

(Reporter: sotaro, Assigned: sotaro)

Details

Attachments

(2 files)

It seems OK to change DPBegin() to async.
Assignee: nobody → sotaro.ikeda.g
Attachment #8837951 - Flags: review?(bugmail)
Comment on attachment 8837951 [details] [diff] [review] patch - Change DPBegin() to async Review of attachment 8837951 [details] [diff] [review]: ----------------------------------------------------------------- What is the advantage of this patch? It's not clear to me why it's needed. And it seems like the success true/false return value is used right now, so I'm hesitant to just take it out without justification. ::: gfx/layers/wr/WebRenderBridgeParent.cpp @@ -189,3 @@ > { > if (mDestroyed) { > return IPC_OK(); Doesn't this codepath return success=false?
Attachment #8837951 - Flags: review?(bugmail)
> What is the advantage of this patch? The patch avoids sync ipc of DPBegin(). It could slow down client side's main thread. > And it seems like the success true/false return value is used right now, > so I'm hesitant to just take it out without justification. mDestroyed check in DPBegin() actually do not work always, since there could be a race condition until HandleDPEnd(). And all WebRenderBridgeParent::Recv**() functions have mDestroyed check, then receiving ipc message since mDestroyed = true is not a problem now. Further, if mDestroyed = true, that WebRenderBridgeParent is going to be destroyed soon. From the above, DPBegin() do not need to return success and could be async.
Comment on attachment 8837951 [details] [diff] [review] patch - Change DPBegin() to async :kats, can you review it again based on comment 4?
Attachment #8837951 - Flags: review?(bugmail)
Comment on attachment 8837951 [details] [diff] [review] patch - Change DPBegin() to async Review of attachment 8837951 [details] [diff] [review]: ----------------------------------------------------------------- OK, that makes sense, thanks!
Attachment #8837951 - Flags: review?(bugmail) → review+
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
It seems to hit RenderThread's existing problem.
Status: REOPENED → RESOLVED
Closed: 9 years ago9 years ago
Resolution: --- → FIXED
(In reply to Sotaro Ikeda [:sotaro] from comment #11) > tryserver result becomes good now. Bug 1337885 seemed to affect to the > failures. That seems surprising since your patch originally landed before 1337885. But ok, it seems green now.
I'm doing another merge from m-c, which picked up the sync-messages changes and caused a build error. We need to delist this message from sync-messages and have it IPC-peer-reviewed.
Attachment #8839471 - Flags: review?(dvander)
Pushed by kgupta@mozilla.com: https://hg.mozilla.org/projects/graphics/rev/e4e9dcee9683 Follow-up to delist a formerly sync message that is now async. r=dvander?
Attachment #8839471 - Flags: review?(dvander) → review+
Target Milestone: --- → mozilla54
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: