Repository navigation
fix(server): avoid holding map iterators across suspension in PCM paths - #489
Merged
Merged
Conversation
📝 WalkthroughWalkthroughCompiler orchestration in compiler.cpp is refactored so module name/PID values are copied from map lookups into local variables before coroutine suspension points (co_await), and these stable copies are subsequently used for cache checks, logging, and dependency compilation dispatch instead of iterators or references. ChangesSuspension-safe compiler lookups
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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
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.
Two spots in the PCM build paths held references into `workspace.path_to_module` (a `DenseMap`) across coroutine suspension points. While a PCM build is awaited, a concurrent `didSave` can insert into or erase from that map; a rehash then invalidates the held iterator, and the resumed coroutine dereferences freed memory (use-after-free — garbage logs at best, crash at worst). The window is realistic: during a module project's warm-up, PCM builds run back-to-back, and adding a new `.cppm` file at that moment triggers the insert.
No behavior change. The race itself cannot be reproduced deterministically in a test; verified by review that no iterator or reference into the map lives across a suspension point, plus a full local build and unit-test run (843 passed). CI runs the full matrix.