Mac: Native crash in CoreFoundation/CFArrayGetCount with any mc>=1.13

[HenryLoenwind]

System Information

MultiMC version: 5.6.12-develop-1624 (also tried stable before)

Operating System: 10.15.6

Summary of the issue or suggestion:

Minecraft versions starting with 1.13, no matter if vanilla or modded, no matter the jvm, will crash when launched through multimc. When capturing the java command and the stdin sent to the onesix launcher and running the same command in a Terminal window, it works fine. (mc 1.12 works)

What should happen:

Java should not crash

Steps to reproduce the issue (Add more if needed):

1. Install multimc
2. Create a vanilla instance, any version 1.13 or higher
3. Press launch

Suspected cause:

I get the same crash outside multimc when I run Minecraft on a new jvm the first time, but there it is accompanied by a security popup about java wanting to monitor keyboard input. When I go to security settings, I then see "java" listed there and can enabled keyboard monitoring. After that it runs fine.

However, it seems when run through multimc, this setting doesn't apply. I neither get a security popup, nor does java (or multimc) get listed in the security settings, nor does manually adding them have an effect.

Logs/Screenshots:

Running fine:

Same instance and jvm inside multimc:

Tested with multiple JVMs, doesn't make any difference:

Here's a crashlog: https://gist.github.com/HenryLoenwind/f2256af0a85bb705345ee296cdb90900

I can produce them for any combination of JVM and Minecraft version you like, these are just the ones I had in front of me just now.

Additional Info:

I've seen the other "crash on mac" tickets. Sadly I don't get as far as those lucky people... ;)

PS: Here is a workaround: https://gist.github.com/HenryLoenwind/134e78a0bfa99bec49c24781b6111bce

[phit]

I was unable to reproduce this on a fresh install of macOS 11.5, freshly installed Java for the first time and ran the game without issues. I wonder if this was fixed somehow by itself at some point, since I've also never seen any support requests for this in the last couple of months.

[HeroOfFire45]

I had the same issue with 1.12 pre 11.5 today, I think it's safe to assume this is more an "out of date OS" issue.