In
msg #6, I asked you which selection you made from the Tools > Ports menu. I have gave a screenshot with red arrow overlay to explain the different selections.
As nearly as I can tell, you *still* have not said which Port selection was used. Why do you withhold this critically important information?
I have full Arduino/java crash report from my system when it’s happened last time. But there is some “sensitive ” data and binary images from my machine and processing.
I only use the Java exception trace, similar to the one you posted on
msg #2. Please post only that part.
Do not post Apple's binary process dumps here. I will *not* use them. The reality is I do not have any way to investigate a MacOS kernel panic. I am not a kernel developer. Even if I was, I do not work for Apple. While Apple does publish some stuff as open source, I have no access to key info needed to debug a MacOS kernel crash, even if I had the knowledge & experience to use such info. I simply can not meaningfully investigate a MacOS kernel panic. Only Apple can do that!
About solving this problem, first I would suggest using the other Ports menu selection. I *still* have to guess, because you will not tell us which one you really used, but from this error my guess is you selected the "Serial ports" section. This really looks like Java was accessing the serial device.
Crashed Thread: 25 Java: EventThread /dev/cu.usbmodem4275401
If you select the "Teensy" section, a completely different access to the port is used. Instead of Java using the JSSC library to access the port, a native "teensy_serialmon" program is run. You should be able to see it if you run "top" in Terminal. This program communicates with Java through stdin/stdout/stderr pipes, which means Java is not doing any hardware access at all.
I would also agree with Theremingenieur, Apple published rather buggy serial drivers 3 years ago with El Capitan. Back when 10.11 was new, many people using Arduino and Teensy and other boards experienced many problems. Apple (mostly) fixed these bugs with Sierra. If your machine is able to upgrade, you should. However, I do know some hardware from 2008 or earlier (like the "cheese grater" MacPro 3,1) can't upgrade beyond 10.11 without unofficial hacks.
But even if you have one of those very old macs that can't upgrade, you certainly *CAN* clearly answer the question of msg #6. You *can* select the "Teensy" port instead of the "Serial port" from the Ports menu, and check that the "teensy_serialmon" is actually running and doing the communication.