Closed Bug 1547864 Opened 1 year ago Closed 1 year ago

Send all data needed to pause at once

Categories

(Core :: Web Replay, enhancement, P5)

enhancement

Tracking

()

RESOLVED FIXED
mozilla68
Tracking Status
firefox68 --- fixed

People

(Reporter: bhackett1024, Assigned: bhackett1024)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

When the server pauses while replaying, there is a bunch of back and forth communication with the replaying process to get all the state the client will need to update the UI and finish pausing: contents of all frames on the stack, and contents of the scripts and objects referenced by those frames. This is inefficient, especially when the replaying process is on a different machine with significant latency.

It would be much better if the replaying process could send the server all this data at once, which can be used to fill in all the necessary ReplayDebugger.Objects, .Scripts, and so forth whose contents will be needed to finish the pause. Right now this pause data is only used for the place the server is currently paused, but in the future it will also be used to cache the state at other places the user could pause, like adjacent step targets and time warp targets.

Type: defect → enhancement
Priority: -- → P5
Pushed by bhackett@mozilla.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/3c5ff599ce3c
Use a single debugger request to gather information needed to pause at a location, r=loganfsmyth.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in before you can comment on or make changes to this bug.