Fix #69: Handle unhandled promise rejections in AdaptiveMemoryManager#124
Merged
thedhanawada merged 1 commit intomasterfrom Mar 20, 2026
Merged
Fix #69: Handle unhandled promise rejections in AdaptiveMemoryManager#124thedhanawada merged 1 commit intomasterfrom
thedhanawada merged 1 commit intomasterfrom
Conversation
checkMemoryPressure() is async but was called from setInterval without awaiting or catching the returned promise. If it threw, the rejection was unhandled — potentially crashing Node.js or silently swallowing errors in browsers. Added .catch() to both the interval callback and the initial check. Fixes #69
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
1 participant
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.
Fix
Added
.catch()handlers tocheckMemoryPressure()calls instartMonitoring()(AdaptiveMemoryManager.js:71-77).checkMemoryPressure()is async but was called fromsetIntervalwithout await or catch. If it threw, the promise rejection was unhandled — potentially crashing Node.js or silently swallowing errors in browsers.Files Changed
core/performance/AdaptiveMemoryManager.js— 6 lines added, 2 removedFixes #69