MemoryError when uploading and starting files multiple times about lego-spikeprime-mindstorms-vscode HOT 5 CLOSED

Hey @J0J0HA , where do you see this MemoryError? If it is in the console from the Hub, what happens if you perform the same action but using LEGO's app?
Another thing you can try (if you haven't done already) is to enable in your vscode settings to compile programs before upload:

from lego-spikeprime-mindstorms-vscode.

Thank you, I'll try that tomorrow.

It is in the console of the Hub. It gives it not if I run it over the SPIKE Prime App directly, it'll work, but if i download it via the SPIKE Prime App, and run it on the Hub, it does not work. I think it's because I'm creating too much objects in the code. But, even if nothing chnaged (but the battery), it does now work for 30-40 downloads rather than 1 as before.
I think activating the compiling will help, but I'd still have one question. Is your plugin optimized for v2/Legacy or for v3? (I use Legacy). I ask this, because the docs say, the main difference is about the file transferring.

I dont think it'll help, put the MemoryError is thrown in programrunner/init "while allocating 163 bytes" The 163 stay all the time, even if the code length changes, but i expirienced that the error is thrown more often if I use multiline strings for block comments as if i put a # on the beginning of every line. So I guess it still depends on how many objects are being created.

from lego-spikeprime-mindstorms-vscode.

If the LEGO app works fine, probably the problem is with the compile since their app by default compiles sources before uploading. But since the error happens in the programrunner which is on the hub, this indicates problem on the hub itself.

As for v2/v3 - the extension works ONLY with v2. You can subscribe to #55 for updates on if/when v3 will be supported.

from lego-spikeprime-mindstorms-vscode.

No further response so closing this one for now. In case you still have problems, please provide more details.

from lego-spikeprime-mindstorms-vscode.

Sorry for not answering, the issue is resolved. It worked since I activated compile, but I still needed to use some less objects.
It is more likely the problem was on the hub, because it also happened when I ran Programs I downloaded through the SPIKE Prime App manually.

Unfortunately, I don't know exactly anymore how the issue got resolved, but I never got the issue again and I am happy with your extension :)

Thank you for your assitance and sorry for not responding again.

from lego-spikeprime-mindstorms-vscode.