New version of JOSM noticably sluggisher and becoming unresponsive

[Vincent Privat]

To troubleshoot performance issues you have to profile the code, for
example with JVisualVM, Java Mission Control or YourKit.
Then you can see what part of the code uses most CPU.

Le dim. 19 août 2018 à 16:23, Éric <gill3t.3ric+osm at gmail.com> a écrit :

> Disabling geotools solved the slugginess for me.
>
> Le 19/08/2018 à 11:35, Jo a écrit :
> > I'm also noticing that JOSM sometimes hangs. In my case it is then
> > consuming >300% processing power. I often see it right after panning the
> > map.
> >
> > I'm beta testing PT_Assistant and can't be sure whether that has
> something
> > to do with it.
>
>