Closed
Bug 1442903
Opened 7 years ago
Closed 6 years ago
Web Replay: Record/replay assertion changes
Categories
(Core :: General, enhancement)
Core
General
Tracking
()
RESOLVED
INVALID
Tracking | Status | |
---|---|---|
firefox60 | --- | affected |
People
(Reporter: bhackett1024, Assigned: bhackett1024)
References
Details
Attachments
(1 file)
1.81 KB,
patch
|
Details | Diff | Splinter Review |
Record/replay assertions can be stuck into the source (usually C++, but JS is also supported) to add checks that the replay is lining up with the recording. Currently there are a fair number of these scattered around the codebase, mostly leftover from previous issues that have since been tracked down. See Part 9b in bug 1422587. This bug will keep track of changes to these assertions. Before landing to m-c they will all (or mostly) be stripped out.
Assignee | ||
Comment 1•7 years ago
|
||
The ThingIndex APIs in RecordReplay.h are used to associate pointer values (which can vary between recording/replay) with unique integer values (which should not vary between recording/replay). This API is flexible but a bit of a footgun because if a pointer was never registered with the API then getting its index can produce a non-deterministic result: the index of some other pointer previously at that address may be returned instead. This patch fixes a couple places where ThingIndex was used on pointers that were never registered, causing bogus divergence reports.
Assignee: nobody → bhackett1024
Assignee | ||
Comment 2•7 years ago
|
||
Assignee | ||
Comment 3•6 years ago
|
||
Closing this bug, all the changes here will be reviewed in separate bugs dependent on bug 1422587.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•