Closed
Bug 1705736
Opened 3 years ago
Closed 3 years ago
We should have profiler marker and label frames for calls to Worker.postMessage
Categories
(Core :: DOM: Workers, enhancement)
Core
DOM: Workers
Tracking
()
RESOLVED
FIXED
90 Branch
| Tracking | Status | |
|---|---|---|
| firefox90 | --- | fixed |
People
(Reporter: florian, Assigned: florian)
Details
Attachments
(1 file)
We have lots of hang reports in BHR data where we are hung in JSStructuredCloneWriter. When looking at the stack, the structured clone happens because of a call to worker.postMessage in the stack. It would be very useful to know for sure which worker is causing these frequent hangs (likely by sending around data that is too large).
|
Assignee | |
Comment 1•3 years ago
|
||
Pushed by fqueze@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ac952451dc01 Add 'Worker.postMessage' profiler markers and label frames to show which worker is involved, r=gerald,dom-worker-reviewers,asuth.
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox90:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•