Closed Bug 1608261 Opened 1 year ago Closed 1 year ago

Shade untraversed and unscanned regions differently on timeline

Categories

(Core Graveyard :: Web Replay, enhancement)

enhancement
Not set
normal

Tracking

(firefox74 fixed)

RESOLVED FIXED
mozilla74
Tracking Status
firefox74 --- fixed

People

(Reporter: bhackett1024, Assigned: bhackett1024)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

When new data is added to a recording, we have to go through a couple steps before we can search for breakpoint hits and so forth in that region. There is one process (the trunk) that runs through the recording and forks off other ones (branches) to sit idle at various points in the recording. These branches are then used to fork off other children that scan each part of the recording.

Currently we show regions of the recording on the timeline which haven't been scanned, but for tuning it will be useful I think to use a darker shade for regions of the recording that haven't been traversed by the trunk child. The attached patch makes this change, along with a fair bit of cleanup to reorganize the code that manages all this status information that is sent up to the client for updating the timeline.

Pushed by bhackett@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/88be64c8dfc0
Shade untraversed and unscanned regions differently on timeline, r=jlast.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla74
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.