JOSM recommends to update to Java 11

[mrgenie]

the problem with this is - in Java 8 I can load tons of data and have a fast experience.

I can even load an are of 100 by 100km and have no problems!

When I go to Java 11 - to get rid of the warning that I should use Java 11 - JOSM becomes basically useless.

I mean even a 10 by 10 km, or 100 times smaller area to work with - GUI just becomes unresponsive and hangs at 25-35% CPU utilization according to the task manager and sticks there for 30 minutes (until I figure I waited long enough and just force close java)

So for now I'm going back to Java 8 and will skip the mere thought about the recommendation on the interface that we should go to Java 11.

It's like telling me I must throw away JOSM and stop using it ROFLMAO

Let me know when the app is actually working under Java 11 - then I'll give it another try.

note this isn't an error - there's no error, no crash.. GUI and the whole app simply stuck using Java 11 on larger areas.

Again, the old java 8 I can load 100 by 100km data from the OSM database and have NO PROBLEMS..

[GerdP]

Can't say much about this without a status report, but it sounds like you may have a 64 bit Java 8 version and a 32bit Java 11.

Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.

Please add all needed information according to this list:

• The required parts of the Status Report from your JOSM.
  • Please, use Report Bug from Help menu and copy & paste.
• Describe what behaviour you expected.
• Describe what did happen instead.
• Describe if and how the issue is reproducible.
• Add any relevant information like error messages or screenshots.

To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.

Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!

[mrgenie]

I flushed the cache, appdata stuff, basically everything and re-installed literally from scratch.

Then everything works smooth again, so I deem my own report then as invalid.

I have to make clear - due to the stability of JOSM thus far - since I first installed 3 years ago and using sometimes stable releases and sometimes the developers versions - I never flushed cash, or any other reset, while over time installing, uninstalling, trying out plugins or removing them and even playing around with my own plugins, icons, the advanced settings tab, etc..

Most likely from all my "experimenting" over the years and given the fact no one else experienced this evidently - that it's just a matter of just starting a clean slate with this app.

Since it always worked very stable for me - thought this to be a glitch as it happened after I made the switch to use java 11 instead of 8. But starting a clean slate java 11 is just as fast - so it's probably all the caching and experimenting over the years to be revealed not in 8 though in 11, though most likely going to 11 isn't the cause - the years of trying out, caching, experimenting, using various versions, even sometimes installing older versions again is then most likely the cause..

So case closed.