-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Infinite build regression in 3.2+ #29326
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
Comments
I've looked at full stack again and for me it looks like problem starts from reportNonexistentProperty call. Then I probably will be able to narrow down repro |
Looks like it is related to noErrorTruncation option. Setting it to false makes build pass again (without errors!) |
Ok, repro is easy: /// <reference path="jquery.js" />
|
Actually, I think real problem here is that compiler spends insane (or significant in case of |
Yeah... error truncation exists for a reason~ types can become arbitrarily complex (and arbitrarily complex to print) so the cutoff can actually become important for perf reasons. Still, I am curious what in the jquery JS file would make us generate such a complex type - normally this kinda thing only happens when someone is doing higher order type system algebra (which a JS file isn't usually capable of). |
We'd really need a repro to assist further |
Retested it and it works fine again starting from v3.5.1. |
TypeScript Version: 3.2.1 - 3.3.0-dev.20190108
Search Terms:
infinite, build, memory
Code
this is something I need help to narrow down
Expected behavior:
project built successfully as it is done in TSC 3.1.6 and below
Actual behavior:
node.exe allocates memory in ~300Mb chunks and release about 280Mb of it repeatedly leading to OOM after some time
Issue occurs after
error check
stage, because if project has build errors, it stops after errors repored.** tsconfig **
tsconfig:
parent tsconfig:
Guys, I think I need some help narrowing down this issue/repro. I can attach to build using debugger, but because it looks like some iterative process and call stack doesn't give me any idea where to look as I'm not really familiar with tsc internals - I think I need some directions what I should check.
Random stacktraces:
The text was updated successfully, but these errors were encountered: