-
Notifications
You must be signed in to change notification settings - Fork 12.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possible regression: Maximum call stack size exceeded when migrating from 3.7.5 to latest version #39059
Comments
We got similar error upgrading TS from
|
I'm also getting a "Maximum call stack size exceeded" error on upgrade from 4.6.0-beta to 4.6.1-rc through 4.63. |
We're also running into this issue with our Angular project. For us it happened when moving for 4.6.1-rc to 4.6.2. Here are the memory profiles for 4.5.5, 4.6.1-rc, 4.6.2 : |
here you have @nscarcella ’s code in playground. |
Angular CLI: 14.2.0 Angular: 14.2.0 Package Version@angular-devkit/architect 0.1402.0 <--- Last few GCs ---> [15680:00000133705CBA10] 267585 ms: Scavenge (reduce) 8065.7 (8244.6) -> 8065.2 (8244.6) MB, 14.7 / 0.0 ms (average mu = 0.218, current mu = 0.028) allocation failure <--- JS stacktrace ---> FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory |
I know this was the issue that was linked from the angular-cli thread, but I feel like the "heap out of memory" issue is probably different from the "maximum call stack size exceeded" mentioned by the OP. We were also seeing the memory leak with Angular 14.1, though tentatively it seems to be behaving better on 14.2.4, maybe related to angular/angular#47508? |
After migrating from 3.7.5 to any later version the attached code makes the compiler fails with the following error:
The same file compiles fine in 3.7.5 and I can't find a way to adapt it to the newer versions.
TypeScript Version: any version above 3.7.5
Search Terms: "Maximum call stack size exceeded" "Range Error" "Regression" "3.8"
Config:
Code
Sorry about the lengthy code, I removed as much unrelated logic as I could and trimmed all methods and fields from the classes so it will be as short as possible while still triggering the error consistently. Removing any of the seemingly trivial classes left prevents the error (not sure why, though) but it's, of course, not a valid option.
Expected behavior: The code builds successfully.
Actual behavior: The compilation fails.
The text was updated successfully, but these errors were encountered: