Closed NealeTools closed 1 month ago
I've not really touched anything regarding how cspect is launched....
Is it safe to assume you've not changed version of cspect and your Macos hasn't been upgraded in-between?
No changes to macOS (10.15.7) or CSpect (2.19.4.4) I can reproduce multiple spawning with every version from v1.11.5+ Earlier versions (v1.11.4 and earlier) appear to successfully kill the active mono process.
This is still an issue in v1.11.8, sorry!
Yeah, this issue is outside of the txt2bas, equally, there was no code change around this logic, my gut says it's either vscode or the OS that's the issue with it launching...
Though, it might be easy to confirm by installing a previous version of the extension to see if the issue repeats.
On Wed, 12 Jun 2024, 19:38 MattN, @.***> wrote:
This is still an issue in v1.11.8, sorry!
— Reply to this email directly, view it on GitHub https://github.com/remy/vscode-nextbasic/issues/58#issuecomment-2163678090, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAADLBBCG7QUHDTZIEOVMRLZHCISTAVCNFSM6AAAAABJG5CH7SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGY3TQMBZGA . You are receiving this because you commented.Message ID: @.***>
Thanks Remy: See comment on Apr 29. The issue started in extension version 1.11.5 onwards, so should hopefully be a simple fix to see what changed between version 1.11.4 and 1.11.5. (Please :-) - the multiple spawning makes it pretty unusable at the moment. I regularly (also now in v.1.11.8) end up with a phantom task that spins up the laptop fans.
hmm, just spotted something. just putting kids down then will push a new version, might be it - not sure why it would be, but it's worth trying
Well… I tried to upload a pre-release, but for some reason, it landed as "real" release. So that one word change is now in 1.11.9 - if you want to give it a try
Perfect! This kills it every time now 👍
Okay, let's close this one.
On prior versions, launching CSpect used kill any current mono instance before launching. On new plugin, this doens't happen and I can inadvertently get a few CSpect running in parallel, slowing each other down, and eating huge laptop resources. Secondly, even when quitting them, sometimes they leave behind this "mono-sgen64" process (two of them) that are massive resource hogs (200% CPU each). On worst case, even when closing laptop to sleep, it left these processing running and fans blowing. ie. They prevented sleep! Hoping this is an easy fix :-)
MacOS 10.15.7 MBPro i7 13 inch.