You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using VSCode on Windows 11 connected to WSL where I have stefterv-processing 4.4.74 installed via snap, and where this extension is also installed. Each time I open VSCode, my Linux processing installation (stefterv-processing 4.4.74) opens as well.
Hi @woodymorrice Thank you for testing it out and finding this issue, I just replicated it on my Windows machine.
I suspect it has to do with the snap sandbox since the extension is trying to start the binary outside of snap. I hadn't implemented support for the snap version of Processing so I suspect, when I fix this on linux it might also fix it within WSL. For now I'll add documentation that the snap version is not yet supported but the portable version is.
I'd recommend using the Windows based setup for now if that's okay with you, or try the portable version within WSL
Activity
Stefterv commentedon May 29, 2025
Hi @woodymorrice Thank you for testing it out and finding this issue, I just replicated it on my Windows machine.
I suspect it has to do with the snap sandbox since the extension is trying to start the binary outside of snap. I hadn't implemented support for the snap version of Processing so I suspect, when I fix this on linux it might also fix it within WSL. For now I'll add documentation that the snap version is not yet supported but the portable version is.
I'd recommend using the Windows based setup for now if that's okay with you, or try the portable version within WSL
SableRaf commentedon Jun 20, 2025
FWIW, this happens for me on macOS and, I believe, on Windows 10 too (not WSL).
On macOS, Processing starts and looks like this in the Dock.
Stefterv commentedon Jun 20, 2025
I just released 76 does it still happen with that version as well?
SableRaf commentedon Jun 20, 2025
That seemed to fix it for me on macOS!