-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Maximum call stack size exceeded (RangeError) #12526
Comments
@BarryDrez can you confirm what version you're using of |
Hi @vince-fugnitto , thanks for the reply. I do not specify this anywhere. In my node modules, II see the following: |
Can you check which version |
@vince-fugnitto It is Version 1.9.1 |
It seems that you're running into #12499 then, thanks for confirming 👍 Until it is fixed you can add a yarn resolution to pin the dependency to the version we use in this repo ( Lines 7571 to 7576 in 23e3df5
|
Thanks a lot. I will try that. |
@vince-fugnitto Just wanted to let you know that this solved the problem. |
@vince-fugnitto Ever since I made this change, the language server is taking a very long time to load. Cleaning doesn't seem to help. Is this related to the resolution? |
@BarryDrez I don't think so, the resolution uses the version we use in this repository already. For which language are you noticing it take time? |
@vince-fugnitto I am noticing this for Java. |
Here is a list of all of my plugins:
|
I tried some earlier versions of the plugins, and now it is starting up faster. |
Bug Description:
Seeing many errors in the browser console:
rpc-message-encoder.ts:151 Uncaught (in promise) Error: Error during encoding: 'Maximum call stack size exceeded'
at MsgPackMessageEncoder.encode (rpc-message-encoder.ts:151:23)
at MsgPackMessageEncoder.request (rpc-message-encoder.ts:137:14)
at RpcProtocol.sendRequest (rpc-protocol.ts:161:22)
at proxy-handler.ts:74:45
The message appears over and over when selecting different lines in the editor and when scrolling.
Steps to Reproduce:
Additional Information
The text was updated successfully, but these errors were encountered: