-
Notifications
You must be signed in to change notification settings - Fork 13.2k
Closed
Labels
Fix AvailableA PR has been opened for this issueA PR has been opened for this issue
Description
🔎 Search Terms
"Maximum call stack size exceeded"
"checkPropertyAccessExpression stack overflow"
"checkNonNullExpression recursion"
"getQuickTypeOfExpression crash"
🕗 Version & Regression Information
Crashes in: 5.7.3, 5.8.3, 5.9.3 (Nightly)
Strict Mode: Only crashes with --strict enabled.
⏯ Playground Link
💻 Code
const [r0Def, r0, r1Def, as, string, r1, r2, r3Def, r3]: boolean = (test as number < string > ).ranges();🙁 Actual behavior
.\ts-versions\nightly\node_modules\.bin\tsc.cmd --strict .\renameDestructuringDeclarationInForOf_mutated_batch12.ts
D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:123214
throw e;
^
RangeError: Maximum call stack size exceeded
at checkExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:80820:27)
at checkParenthesizedExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:80869:12)
at checkExpressionWorker (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:80932:16)
at checkExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:80826:32)
at checkNonNullExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:74858:29)
at checkPropertyAccessExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:74937:162)
at checkExpressionWorker (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:80917:16)
at checkExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:80826:32)
at checkNonNullExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:74858:29)
at getQuickTypeOfExpression (D:\do\typeFuzz\ts-versions\nightly\node_modules\typescript\lib\_tsc.js:80797:139)
Node.js v22.19.0
🙂 Expected behavior
The compiler should not crash.
Additional information about the issue
No response
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Fix AvailableA PR has been opened for this issueA PR has been opened for this issue