Closed
Bug 1491816
Opened 6 years ago
Closed 6 years ago
deal with unresponsive content processes in ChromeUtils.requestPerformanceMetrics()
Categories
(Toolkit :: Performance Monitoring, enhancement)
Toolkit
Performance Monitoring
Tracking
()
RESOLVED
FIXED
mozilla64
Tracking | Status | |
---|---|---|
firefox64 | --- | fixed |
People
(Reporter: tarek, Assigned: tarek)
References
Details
Attachments
(1 file)
Right now a call to ChromeUtils.requestPerformanceMetrics() waits for all content process to return their data. But if one is unresponsive (slow script, etc.) it will hold the promise. We need to deal with this issue, and if possible report back on which content process is acting out, so about:performance can use that information
Assignee | ||
Updated•6 years ago
|
Assignee: nobody → tarek
Assignee | ||
Comment 1•6 years ago
|
||
Adds a timout that will resolve the promise to return even if we did not get an answer from all children. MozReview-Commit-ID: FFLwAUkkYos
Assignee | ||
Comment 2•6 years ago
|
||
Florian, unfortunately I have not found a good mechanism in IPC to mock the delay in content process or workers. Could you give us your STRs this issue so we can manually verify that the timeout is correctly triggered ? Thanks
Flags: needinfo?(florian)
Comment 3•6 years ago
|
||
(In reply to Tarek Ziadé (:tarek) from comment #2) > Could you give us your STRs this issue so we can manually verify that the > timeout is correctly triggered ? A page containing this piece of JS should make its content process unresponsive: function fn() { let start = Date.now(); while (Date.now() - start < 5000) ; // do nothing setTimeout(fn, 0); } fn(); It should be possible to cover this with an automated test, right?
Flags: needinfo?(florian)
Assignee | ||
Comment 4•6 years ago
|
||
Before commenting here I tried a similar test with workers but could not get it to work. Your example seems to work though, thanks a lot! working on adding that
Assignee | ||
Updated•6 years ago
|
Blocks: new-about-performance-m1
Assignee | ||
Comment 5•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=7807bede28e7ea9babd4e6ab04e9f2bc74dfbc75
Assignee | ||
Comment 6•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=2a63021f697708440de6141b3b7f66d34f29756c
Assignee | ||
Comment 7•6 years ago
|
||
https://treeherder.mozilla.org/#/jobs?repo=try&revision=6b56878fc3146a427b6b7a1047c83d4dddd6940f
Pushed by tziade@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8958a60dd824 deal with unresponsive content processes in ChromeUtils.requestPerformanceMetrics() - r=baku
Comment 9•6 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/8958a60dd824
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox64:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
You need to log in
before you can comment on or make changes to this bug.
Description
•