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
Memory leak with vue-tsc #2210
Comments
|
Hi, thanks for the fast response!
|
The most likely reason is that there are too many code (especially .js), so the memory usage increases proportionally. Are you sure 12371 files is a normal number for your project? If yes, you might consider splitting the project and including them by multiple tsconfigs, changing the execution of a one time tsc to multiple times tsc execute against multiple smaller tsconfigs: https://github.com/microsoft/TypeScript/wiki/Performance#performance-considerations And you can try to refer to #2214 author's method to disable allowJs.
See #2214 (comment) |
Closed, as this is not a problem that Volar seems to be able to solve. Also, to check that the project correctly contains the necessary files, you can use https://marketplace.visualstudio.com/items?itemName=johnsoncodehk.vscode-tsconfig-helper. |
Hi, I'm running into a memory problem while attempting to use
vue-tsc
on a very large codebase. A similar issue was discussed here, #1106. I've been trying to reproduce the issue in a separate repo, but so have not been able to.Here is my current setup
I've tried updating node and typescript to latest versions, but that still produced the same error. For now, we've been able to side-step the issue by setting node options
--max-old-space-size=7168
, but this problem is still causing friction elsewhere with the team and in our CI pipeline. Any help would be greatly appreciated.The text was updated successfully, but these errors were encountered: