fix: Issue where ng build never stops#1112
Merged
Merged
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
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.
Closes #1111
This pull request addresses a known memory leak issue in Angular CLI by ensuring the build process exits cleanly after completion. The main change is the addition of a workaround to force process termination, which will be removed once the issue is fixed upstream.
Process termination workaround:
setTimeoutcall to forcefully exit the process after the build finishes, preventing memory leaks related to Angular CLI (see @angular/build: leaves esbuild service child alive after watch:false build angular/angular-cli#33201). This is a temporary measure until the upstream issue is resolved.