-
-
Notifications
You must be signed in to change notification settings - Fork 207
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
Any way to increase memory for VS code extension? #2725
Comments
You could probably use the svelte.language-server.runtime-args config to increase the memory limit. But this is most likely a misconfiguration with your include and exclude config in the tsconfig.json. You need to exclude or not include the build outputs. Normally, there should be a size check to prevent crashes; maybe you disabled it while debugging the size limit warning? |
I don't think so? where would I have disabled it? |
This does not appear to work
Still seems like it's crashing around 4gb |
I still think it is more likely to be a problem with your tsonfig.json. You need to check if the "include" config matches any build output. 4000 source files in a single project doesn't sound right. |
After having investigated this further, I don't think this is a tsconfig issue, I can't find any build output as part of the tsconfig, it is quite a large project however. I think the issue is downstream from this one https://x.com/arktypeio/status/1905293040064790541 ie a typescript issue when inferring types from in our case zod objects. We do this quite a lot. While waiting for a resolution for this do you have any other suggestions for increasing the memory other than |
If that is the case, it sounds like a typescript issue. Then you either have to report to TypeScript or ArkType. You might have to check when this started to happen, and maybe you can narrow down the files that might be the problem. |
I agree, it's a typescript issue and it sounds like it's being worked on on the typescript side, so it'll most likely go away eventually, and you are right, I could fix it on my side by reducing our usage of type inference to reduce the typescript overhead. all that being said, it would be nice to be able to temporarily change the memory for the plugin, so it can still work while either waiting for a typescript fix or reducing our reliance on what's causing the issue. |
@AndreasHald. |
My extension crashes with the following
I know this is most likely related to excessive use of types and should probably be debugged why it's attempting to use so much memory, but in the meantime - is there anyway I can simply give the extension 8 or 16gb of memory?
The text was updated successfully, but these errors were encountered: