recursiveTypeRelatedTo_DepthLimit - diagnosing poor performance in TS 4.5+ #47208
Assignees
Labels
Bug
A bug in TypeScript
Duplicate
An existing issue was already created
Rescheduled
This issue was previously scheduled to an earlier milestone
Milestone
Comments
|
I've observed the following behavior which I believe is related to this bug: The following compiles without any problem type T = 1 | Promise<T> | T[];
export function myFunction(param: T) {
const awaited = param
}But awaiting the input value as follows results in the error type T = 1 | Promise<T> | T[];
export function myFunction(param: T) {
const awaited = await param
} |
RyanCavanaugh
added
the
Rescheduled
|
According to the upstream tracker, this issue was fixed in 4.6+: Vincit/objection.js#2178 (comment) I can't seem to reproduce it either; @JeongJuhyeon can you reproduce this in the latest version of TypeScript? If so, can you post a full repo (or lockfile at least) so I can retry it? |
|
Using the info on Vincit/objection.js#2177, I was able to bisect this as being fixed by #47341, which fixed #47142, which was explicitly for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
🔎 Search Terms
RangeError: Maximum call stack size exceeded
recursiveTypeRelatedTo_DepthLimit
Vincit/objection.js#2177
Vincit/objection.js#2178
🕗 Version & Regression Information
💻 Code
package.json
code
Default tsconfig.
🙁 Actual behavior
Open VS Code. Place cursor after the period on the query line. Invoke suggestions. "Loading.." takes about 5 seconds. At times hovering over "k" to look at the type also shows the same slow "Loading.." behavior. TS Server log shows this:
At other times it shows something like this
I've used --generateTrace and had a look at it. There is a "recursiveTypeRelatedTo_DepthLimit" event during structuredTypeRelatedTo which I'm guessing may be the underlying issue. Is this the likely culprit? What would be the best way to diagnose this? Also, why is TSC fast while tsserver inference is slow? The type-checking part of the compliation (checkSourceFile in the trace) only takes 1.5 seconds.
The text was updated successfully, but these errors were encountered: