Port breakpoint-related changes from Chromium's v8 #108
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bhackett1024
approved these changes
Jul 14, 2025
…issing-breakpoint-locations-in-node-recordings-in-the-for
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should address https://linear.app/replay/issue/PRO-1475/missing-breakpoint-locations-in-node-recordings-in-the-for-ofs-head because this PR deduplicates breakpoints added to the same source position (as it ports replayio/chromium-v8#189 )
In addition to that, to make the port easier~ (we touched related places in a couple of the most recent PRs) I decided to port those PRs too:
replayio/chromium-v8#267
replayio/chromium-v8#268
replayio/chromium-v8#214
replayio/chromium-v8#269