Hacker News new | ask | show | jobs
by bzzzt 824 days ago
It's not a problem that breaks all JVM based software instantly. So maybe Apple tests but not long enough to trigger this issue.

I really don't know what Apple would be 'warning' against. Don't use Java? There are tens of thousands of business and development tools depending on the JVM. Blocking Java would diminish the value of macOS tremendously and doing so without warning would open Apple up to lots of lawsuits.

1 comments

>It's not a problem that breaks all JVM based software instantly.

Do you know how long it takes to reproduce? The OP was light on details here. I assume that a memory access issue with the JIT would pop up pretty quickly, though.

I'm running an Eclipse development environment that's regularly compiling a huge codebase. Had 2 crashes this week after updating so less than once a day. That's assuming it isn't an Eclipse bug ;)
Just being curious: With or without having created a hs_err_pid<pid here>.log? Why do I ask: Ten days now on 14.4. and cannot see any change in Eclipse and Tomcat behaviour.
And yes, I did just now. I had to work for 10 hours to let Eclipse crash... No hs_err. Just the macos problem report popping up.