Closed
Bug 1594861
Opened 5 years ago
Closed 5 years ago
Defer fetching frames
Categories
(DevTools :: Debugger, enhancement, P2)
DevTools
Debugger
Tracking
(firefox72 fixed)
RESOLVED
FIXED
Firefox 72
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: jlast, Assigned: jlast)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
What were you doing?
Looking at the performance profiles, one of the expensive operations is fetching the frames and then mapping them.
We could save some time if we first handle the paused packet with the first frame and then fetch the call stack and map it.
|
Assignee | |
Comment 1•5 years ago
|
||
Pushed by jlaster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/cbd92213095a Defer fetching frames. r=bhackett
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox72:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 72
|
||
Updated•5 years ago
|
Assignee: nobody → jlaster
|
|
Assignee | |
Comment 4•5 years ago
|
||
The 3.8% regression on pause was expected. This patch defers fetching the frames, which does delay showing the call stack to the user.
The reason we do this is that we think it is more important to show the user the paused line and initial paused frame.
You need to log in
before you can comment on or make changes to this bug.
Description
•