121–130 of 160 posts
Earlier quoted context omitted.
It said it affected back to Java 8, so seems like this design has been there for a while, and since older versions are EOL, any Java level fix would not be patched back.
I wonder what that means for the Android SDK, which AFAIK requires an ancient Java8 runtime for the command line SDK tools on macOS.
Earlier quoted context omitted.
So MacOS is trying to be smart, changes their API, and now we're blaming the JVM for doing something we don't understand? At least they could have provided a path back to the old behavior.
macOS is trying to keep its systems safe. Can’t leave the back door open for few who were used to it.
Earlier quoted context omitted.
> it seems highly unlikely that the macos people don't test anything on the jvm during acceptance. I would be surprised if they do to be honest (Apple doesn't even catch obvious bugs in the new macOS settings panel, which really makes me wonder if there is a software QA process at all). For 3rd party apps they seem to rely on the software vendors to holler if a macOS update breaks their app. That's why the macOS prer…
What is the bug in the new System Settings panel?
Don't even get me started on Screen Time bugs...
Earlier quoted context omitted.
> it seems highly unlikely that the macos people don't test anything on the jvm during acceptance. I would be surprised if they do to be honest (Apple doesn't even catch obvious bugs in the new macOS settings panel, which really makes me wonder if there is a software QA process at all). For 3rd party apps they seem to rely on the software vendors to holler if a macOS update breaks their app. That's why the macOS prer…
What is the bug in the new System Settings panel?
One is that occasionally there's an error popup "Extension process Network(4433) exited." just when clicking on the 'DNS servers' search result.
The other is that when accidentally hitting "Enter" after entering a new DNS server address the entire DNS Server subpanel will close even though I want to enter a second address (which sucks from a user perspective, but might even be consistent with the UX guidelines, but OTH I would expect pressing Enter on a text input box would not close the UI panel which contains the text input box, but maybe that's just me). But then clicking on the previous search result 'DNS servers' to open the DNS servers panel again, the click does nothing this time.
One has to clear the search box, enter the search term again, perform a new search, and then click the search result 'DNS servers' again to get the subpanel for entering DNS server addresses.
I guess the search is also broken like this for other subpanels, but changing the DNS servers is about the only situation where I'm using the search box.
In the old settings panel all that worked as expected (and apart from that, everything also was a lot snappier, somehow Apple engineers managed to create simple Settings window that suffers from performance problems, but again, different issue).
Earlier quoted context omitted.
It's not terminating directly. I've seen a few IDE crashes this week, less than one per day, but since there's no log there's no easy way to determine it's related to a macOS change.
https://youtrack.jetbrains.com/issue/JBR-6802 The JetBrains team has already figured it out as well.
Earlier quoted context omitted.
I feel like preventing illegal writes to protected memory is less "breaking user space" and more "protecting all space". This is like arguing to allow the guy who can't drive and just pin-balls his way down the freeway bouncing of other cars, because to prevent him from driving would be to take away his personal freedoms.
There was no conceivable version of a road system where that behavior would ever be okay. However, it's not only conceivable but, apparently standard practice in systems programming, to "Try and Fail" instead of "Only Proceed if allowed". So, if we want a tortured metaphor what JVM is doing is like trying to pass a turnstile to see if the pass is still valid so that on the happy path it saves the extra check. Now App…
That doesn't mean it doesn't happen.
Are you suggesting that the approach taken here was at one point a documented acceptable approach, according to Apple?
Earlier quoted context omitted.
No. Oracle will not fix jre8 because it's too old. Oracle will not fix corretto jre, because it's not theirs.
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?
Earlier quoted context omitted.
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.
>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.