Repository navigation
assert,util: fix stale nested cycle memo entries - #62509
Merged
nodejs-github-bot merged 1 commit intoApr 9, 2026
Merged
Conversation
Temporary nested cycle-tracking entries could remain in the memory set after a successful comparison. If a later sibling comparison reused one of those objects, deepStrictEqual could incorrectly fail for equivalent structures. This cleans up the temporary nested entries after the nested comparison returns. Fixes: nodejs#62422
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #62509 +/- ##
==========================================
- Coverage 89.77% 89.71% -0.07%
==========================================
Files 673 692 +19
Lines 203840 214043 +10203
Branches 39180 41058 +1878
==========================================
+ Hits 182998 192024 +9026
- Misses 13156 14095 +939
- Partials 7686 7924 +238
🚀 New features to boost your workflow:
|
ljharb
approved these changes
Mar 30, 2026
Collaborator
Temporary nested cycle-tracking entries could remain in the memory set after a successful comparison. If a later sibling comparison reused one of those objects, deepStrictEqual could incorrectly fail for equivalent structures.
This cleans up the temporary nested entries after the nested comparison returns.
Fixes: #62422