JOSM on OpenSuSE really slow

[berndw]

What steps will reproduce the problem?

1. start JOSM
2. load some data
3. wait for rendering
4. moving or changing something take up to 30-60 secs

What is the expected result?

LOL, should be as faat as before

What happens instead?

Please provide any additional information below. Attach a screenshot if possible.

This happens since some weeks, maybe 3 of 4 times.
i have made no changes on my JOSM.conf, my tumbleweed system is up to date

Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2024-07-30 15:13:18 +0200 (Tue, 30 Jul 2024)
Revision:19160
Build-Date:2024-07-31 01:30:32
URL:https://josm.openstreetmap.de/svn/trunk

Identification: JOSM/1.5 (19160 de) Linux openSUSE Tumbleweed
Memory Usage: 7583 MB / 7583 MB (7310 MB allocated, but free)
Java version: 21.0.4+7-suse-1.1-x8664, N/A, OpenJDK 64-Bit Server VM
Look and Feel: javax.swing.plaf.metal.MetalLookAndFeel
Screen: :0.0 1920x1080x[Multi depth]@60Hz (scaling 1.00×1.00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→16×16, 32×32→32×32
Environment variable LANG: de_DE.UTF-8
System property file.encoding: UTF-8
System property sun.jnu.encoding: UTF-8
Locale info: de_DE
Numbers with default locale: 1234567890 -> 1234567890
Desktop environment: KDE
Java package: java-21-openjdk:x86_64-21.0.4.0
apache-commons-logging: apache-commons-logging:noarch-1.2
VM arguments: [--add-exports=java.base/sun.security.action=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.plugins.jpeg=ALL-UNNAMED, --add-exports=java.desktop/com.sun.imageio.spi=ALL-UNNAMED, -Dsun.java2d.opengl=false]

Plugins:
+ Mapillary (1769)
+ OpeningHoursEditor (36258)
+ PolygonCutOut (v0.7.3)
+ apache-commons (36282)
+ continuosDownload (103)
+ editgpx (36126)
+ ejml (36176)
+ geotools (36273)
+ jackson (36273)
+ jaxb (36118)
+ jts (36004)
+ merge-overlap (36178)
+ notesolver (0.5.0)
+ opendata (36298)
+ poly (36282)
+ reltoolbox (36298)
+ reverter (36256)
+ tageditor (36298)
+ terracer (36298)
+ turnlanes (36298)
+ turnlanes-tagging (0.0.5)
+ turnrestrictions (36298)
+ utilsplugin2 (36298)

Tagging presets:
+ https://www.openrailwaymap.org/josm-presets/de-signals-eso.zip
+ https://josm.openstreetmap.de/josmfile?page=Presets/Stolpersteine&zip=1

Last errors/warnings:
- 00014.813 E: unable to find dependency jaxb for plugin geotools
- 00014.813 E: unable to find dependency jaxb for plugin opendata

[GerdP]

Your status report shows

Memory Usage: 7583 MB / 7583 MB (7310 MB allocated, but free)

means that JOSM uses all available memory. So when you "load some data" it seems to be quite a lot?

[skyper]

Yes, if JOSM runs out of memory or the system starts swapping it is no fun. Note that there was a bug with wireframe mode which was just recently fixed: #23828.
If you have more system memory available, you could assign more memory for JOSM on startup but it would be really interesting if you are loading huge data or if JOSM core or a plugin is leaking memory. For that we need more info about the loaded data.

[berndw]

Made a short test,
It happened, without trying to load pictures or sat images, only with the enabled default style.
The downloaded map data cover an area of 200 by 300 m

[stoecker]

Well, I have a similar system and everything is fine. So it's something on your system.

Steps you can proceed with:

• Try installing java22 instead of java21, maybe it helps (probably not, but it is worth a try).
• Try with a fresh cache (remove ~/.cache/JOSM directory)
• Try with fresh config (rename ~/.config/JOSM directory and ~/.local/share/JOSM) or use JOSM reset prefs function (after making a backup!) - redo your settings step by step (not too many at once).

If first two steps help, please tell us. If the third step helps we'd like to know what the differences between a working and non-working config are, so we can prevent similar problems.

[stoecker]

Your're using some sort of a download script? Please try josm package instead (wiki:Download#Opensuse).

[taylor.smock]

Is this still a problem (@berndw)? If it is, can you attach a profiler to JOSM? I use ​https://github.com/async-profiler/async-profiler via IntelliJ, but it is possible to use async-profiler by itself. Please upload the output.

Depending upon the exact problem we may be more interested in CPU samples or Memory allocations. I typically do both, since some paths make a lot of memory allocations which then force a "stop-the-world" event for the memory garbage collector. That is very expensive if it happens often.

As stoecker indicated in comment:4, something in the JOSM preferences may be the cause. Do not upload your preferences file here though -- it may contain sensitive information like OSM OAuth tokens, which can be used to impersonate you.