Closed Bug 1579319 Opened 5 years ago Closed 5 years ago

Distinguish objects and frames from different locations

Categories

(Core Graveyard :: Web Replay, enhancement)

enhancement
Not set
normal

Tracking

(firefox71 fixed)

RESOLVED FIXED
mozilla71
Tracking Status
firefox71 --- fixed

People

(Reporter: bhackett1024, Assigned: bhackett1024)

References

Details

Attachments

(1 file)

Right now, ReplayDebugger objects, frames, and so forth are associated with the current pause, and have their contents cleared out so that they are unusable when the debugger unpauses. It would be nice to improve this behavior, so that objects can be used even when the debugger is not paused at the point they came from.

The immediate need for this is to improve handling of messages logged by the console and logpoints. Right now we have a separate ReplayDebuggerObjectSnapshot class for this, but it is clunky, duplicates functionality from the normal object case, and only works well with vanilla objects and arrays. By distinguishing objects logged to the console from objects that are part of some debugger pause, we can use normal ReplayDebuggerObjects in the former case. Logged objects still can't be fully inspected (we can't send queries to the replaying process to access contents not included in the preview) but this functionality could be extended in the future to support that.

Pushed by bhackett@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/5469ca5999ab Distinguish objects and frames from different locations, r=jlast.
Depends on: 1579583
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla71
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: