Has anyone been able to run Monkey C extension 1.1.1 on a Mac without problems?

I didn't notice any problems

Yes same issue here. MacBook Pro with an M2 Pro chip. Complains also when opening ERA viewer and other tools

Same story here. Reverting to 1.0.11 every time as a workaround. (I'm also using M1 Mac)

Oops! I actually do have a problem. I didn't realize it until now.

I have at least 1 app that doesn't work any more with the VSC Monkey C extension version 1.1.0 or 1.1.1. But other apps that I worked on recently do work.

So this bug in the extension does somehow depend on something in the project that is open. My 1st suspicion is that maybe something in .vscode/ or in the workspace tab of the extension config is causing this.

In the app where it doesn't work I have:

.vscode/launch.json (but I do have it in every project, though usually it's a copy&pasted "empty" skeleton just so that when I click Run it'll pop up the device selection list, and in this project it's a but more complicated)

.vscode/settings.json: I only have this file in a few project, one of them is this problematic project.

WOW!

After I downgraded to 1.0.11, then tried 1.1.0 and then back to 1.1.1, now Run does seem to work HOWEVER now another bug started to happen, that was talked about in the forum in the past month:

ERROR: MyApp/default.jungle:7: IOException: MyApp: Too many open files in system

But I don't have any file called default.jungle in my whole hard disk!

And after closing the project window and reopening it, the same problem is back... nothing works. i.e when I click on Run > Run Without Debugging I only see this spinning in the bottom of the VSC window for a few seconds:

Garmin should finance you to share your code in order to fix the bug. 

flocsy🤠 said:

But I don't have any file called default.jungle in my whole hard disk!

default.jungle should be generated in the SDK bin folder if you successfully build at least once. Perhaps the problem is that it's failing to be generated (for the new SDK, if you recently switched to it), and the extension is trying to find it in the project folder?

However, I would expect you to have default.jungle present in all your older SDKs' bin folders (unless ofc this file is not really necessary for anything - Garmin does claim this file is only for reference).

Perhaps it wasn't necessary in the past, but it is now?

ReedWorks said:

It causes weird errors to be displayed (e.g. too many open files)

ReedWorks said:

When I reverted to version 1.0.11 everything is back to normal, works as it should.

flocsy🤠 said:

HOWEVER now another bug started to happen, that was talked about in the forum in the past month:

ERROR: MyApp/default.jungle:7: IOException: MyApp: Too many open files in system

Hmmm wow super interesting that in the other thread, someone suggested reverting to an older version of the Monkey C extension (amongst a ton of other things to try), and that advice was completely ignored in favour of the OP having a convo with themselves. What were their words? "I didn't see any suggestions that were helpful", or something like that.

OK, I feel like I have a clue: with the latest version of the extension, after you just open the project (and get the extension loaded), it (runtime-wise it's "Code Helper (Plugin).app") opens every single file in the project directory as well as in Garmin SDK/Devices - that's clearly visible with e.g. Activity Monitor or lsof. Combined with the some cases where "bin" folder contained many files in my case it basically (I guess) get above the limit of open file descriptors - that's kind of in sync with some error messages produced in the bad scenario. I noticed it because I happened to have around 15K files in bin directory and after deleting those the problem disappeared. Please also read below.