SDK manager keeps not responding

I don't think JDK version can be too high. Every JDK can pretend to be any lower version IMHO.

Yes. It would be compatible with a lower version generally. That just was a guesss.

thanks for all your input folks, but its a bug with the SDK, nothing to do with JDK version.

forums.garmin.com/.../activity-recording-session-start-crashes-the-app-and-simulator-on-sdk-6-4-0

SDK manager still keeps not responding on M3 chip 

please define "not responding". I just opened SDK manager on M3 Pro, Sonoma 14.7.1 and it seems to work

But after maybe 10 minutes, it works.

But what do I do to reproduce it? I just opened SDK manager from VSC, it did the usual updated to check if there's anything new, and then I closed it (because there's nothing new)

I opened the SDK manager from the dock. The "NOT RESPONDING" occurs. Maybe you can try this way. SDK manager seems to load too many resources when being initialized which could cause NOT RESPONDING.

I know this is a very old comment but since this thread was necro'd:

flocsy🤠 said:

I don't think JDK version can be too high. Every JDK can pretend to be any lower version IMHO.

That's not a matter of opinion and it's not true. Yes, older Java apps will generally run on newer JDKs, but it's absolutely not the case that "every jdk can pretend to be any lower version".

As a Java dev, if you are building software with the JDK, your JDK version can definitely be too high. e.g. A codebase meant for Java 11 may refuse to compile under Java 17.

As an end user, if you have an old Java app, it may not run on a newer JDK due to removed APIs [for example]

I think there's good reasons that:

- there's dev tools to manage multiple JDKs. If "every jdk can pretend to be any lower version", it would only be necessary for devs to install the latest

- end users have long been able to have multiple JRE/JDK installations on the same computer. Same comment as previous point

- Java applications meant for end users will sometimes package their own version of Java to be installed alongside the app

As far as CIQ goes, people have found that certain older major versions of Java seem to produce faster compilation times than certain newer major versions. (Nonetheless, I still use a newer LTS version for CIQ. One time I found that updating a newer major release to its latest minor version fixed a compilation speed issue, but that's pretty anecdotal.)