4 ms·

I just bought a MacBook Pro with the M3 Max chip and installed MATLAB R2023b. Sonoma 14.3 is in place. As a requirement, I had to also install Corretto 8. MathW

I just bought a MacBook Pro with the M3 Max chip and installed MATLAB R2023b. Sonoma 14.3 is in place. As a requirement, I had to also install Corretto 8. MathWorks only supports the Java 8 JRE included with Amazon Corretto 8. I am already having several problems in MATLAB with his new setup. Can I assume that updating to Sonoma 14.4 might very well cause even more problems? I really don't understand any of this.

dimask 3y ago
I would not update for the time being. If it works it will probably break, if it is broken it may break more. Btw what sort of problems are you facing? I have had problems with closing figures, but figured it out eventually with a workaround [0]. [0] https://se.mathworks.com/matlabcentral/answers/2027964-matlab-crash-on-sonoma-macos-14-0#answer_1369044 https://se.mathworks.com/matlabcentral/answers/2027964-matla...
xcv123 3y ago
".. is affecting all Java versions from Java 8 to the early access builds of JDK 22. There is no workaround available .." Do not update until Apple fixes the issue.
- ls612 3y ago
  Is it Apple or Oracle who should rightly be fixing this issue?
  - xcv123 3y ago
    It's a bug in macOS and it breaks POSIX compliance. Oracle can develop a workaround but Apple should fix it in their next update.
    - sunshinerag 3y ago
      bug? POSIX compliance? How?
      - xcv123 3y ago
        When a kernel update breaks all JVM versions starting from Java 8, the kernel devs fucked up. Even worse when the breaking change is in the final production release only and not the beta release. Completely obvious that this is a bug. Segmentation fault should trigger SIGSEV, not SIGKILL. They changed the behaviour of the kernel which broke the JVM and any other applications that are designed according to the POSIX standards. https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/V...
        kingds 3y ago
        right, seems like sort of a no brainer that if a minor version bump of an OS completely breaks JDK8, that’s on the OS developer.
- e40 3y ago
  Isn’t this something Oracle will be fixing? Seems like it from other comments here.
  - viraptor 3y ago
    No. Oracle will not fix jre8 because it's too old. Oracle will not fix corretto jre, because it's not theirs.
    - e40 3y ago
      They may not fix it, but my understanding is they are relying on undocumented features and that's always a crap shoot. My company does low-level language stuff and we've been burned like this, too. We decided not to trade performance for compatibility in the last decade or two. EDIT: maybe not undocumented, but undefined behavior?
      - xcv123 3y ago
        Documented in the POSIX specification. It is a kernel bug.

dimask 3y ago

I would not update for the time being. If it works it will probably break, if it is broken it may break more. Btw what sort of problems are you facing? I have had problems with closing figures, but figured it out eventually with a workaround [0]. [0] https://se.mathworks.com/matlabcentral/answers/2027964-matlab-crash-on-sonoma-macos-14-0#answer_1369044 https://se.mathworks.com/matlabcentral/answers/2027964-matla...

xcv123 3y ago

".. is affecting all Java versions from Java 8 to the early access builds of JDK 22. There is no workaround available .." Do not update until Apple fixes the issue.

ls612 3y ago
Is it Apple or Oracle who should rightly be fixing this issue?
- xcv123 3y ago
  It's a bug in macOS and it breaks POSIX compliance. Oracle can develop a workaround but Apple should fix it in their next update.
  - sunshinerag 3y ago
    bug? POSIX compliance? How?
    - xcv123 3y ago
      When a kernel update breaks all JVM versions starting from Java 8, the kernel devs fucked up. Even worse when the breaking change is in the final production release only and not the beta release. Completely obvious that this is a bug. Segmentation fault should trigger SIGSEV, not SIGKILL. They changed the behaviour of the kernel which broke the JVM and any other applications that are designed according to the POSIX standards. https://pubs.opengroup.org/onlinepubs/9699919799/functions/V2_chap02.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/V...
      - kingds 3y ago
        right, seems like sort of a no brainer that if a minor version bump of an OS completely breaks JDK8, that’s on the OS developer.
e40 3y ago
Isn’t this something Oracle will be fixing? Seems like it from other comments here.
- viraptor 3y ago
  No. Oracle will not fix jre8 because it's too old. Oracle will not fix corretto jre, because it's not theirs.
  - e40 3y ago
    They may not fix it, but my understanding is they are relying on undocumented features and that's always a crap shoot. My company does low-level language stuff and we've been burned like this, too. We decided not to trade performance for compatibility in the last decade or two. EDIT: maybe not undocumented, but undefined behavior?
    - xcv123 3y ago
      Documented in the POSIX specification. It is a kernel bug.