id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
22071	JOSM recommends to update to Java 11	mrgenie	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.."	defect	closed	normal		Core		invalid