[DevTools] Throw an error when attempting to clone non-existent node#35702
Merged
[DevTools] Throw an error when attempting to clone non-existent node#35702
Conversation
eps1lon
approved these changes
Feb 5, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
There is an existing issue with serialisation logic for the traces from Profiler panel.
I've discovered that
TREE_OPERATION_UPDATE_TREE_BASE_DURATIONoperation for some reason appears earlier in a sequence of operations, before theTREE_OPERATION_ADDthat registers the new node. It ends up cloning non-existent node, which just creates an empty object and adds it to the map of nodes.This change only adds additional layer of validation to cloning logic, so we don't swallow the error, if we attempt to clone non-existent node.