Opened 4 years ago
Last modified 3 years ago
#20666 new defect
In opposite to the previous version (17428) the latest Version (17580) slows down massively on my system after a few minutes of editing until being totally unresponsive
| Reported by: | tux67 | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core imagery | Version: | |
| Keywords: | template_report performance memory | Cc: |
Description
What steps will reproduce the problem?
- just open JOSM (data in report below) and start changing / adding
What is the expected result?
Responsive System that allows to save the work
What happens instead?
JOSM slows down massively until being no longer responsive.
Please provide any additional information below. Attach a screenshot if possible.
Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2021-03-17 18:58:40 +0100 (Wed, 17 Mar 2021)
Revision:17580
Build-Date:2021-03-17 17:59:56
URL:https://josm.openstreetmap.de/svn/trunk
Identification: JOSM/1.5 (17580 de) Linux openSUSE Leap 15.2
Memory Usage: 950 MB / 950 MB (6 MB allocated, but free)
Java version: 11.0.10+9-suse-lp152.2.9.1-x8664, Oracle Corporation, OpenJDK 64-Bit Server VM
Look and Feel: com.formdev.flatlaf.FlatDarculaLaf
Screen: :0.0 1920×1080 (scaling 1,00×1,00)
Maximum Screen Size: 1920×1080
Best cursor sizes: 16×16→16×16, 32×32→32×32
Desktop environment: KDE
Environment variable LANG: de_DE.UTF-8
Dataset consistency test: No problems found
Plugins:
+ AddrInterpolation (35640)
+ FixAddresses (35640)
+ HouseNumberTaggingTool (35640)
+ OpeningHoursEditor (35640)
+ PicLayer (2a9aa7a)
+ RoadSigns (35640)
+ apache-commons (35524)
+ apache-http (35589)
+ areaselector (368)
+ austriaaddresshelper (1597341117)
+ buildings_tools (35669)
+ continuosDownload (91)
+ ejml (35458)
+ fieldpapers (v0.5.0)
+ flatlaf (35703)
+ geochat (35640)
+ geotools (35458)
+ imagery_offset_db (35640)
+ javafx-unixoid (35655)
+ jaxb (35543)
+ jna (35662)
+ jts (35458)
+ log4j (35458)
+ markseen (14)
+ measurement (35640)
+ opendata (35640)
+ print (35640)
+ pt_assistant (2.1.10-80-g7d9bba3)
+ public_transport (35640)
+ reltoolbox (35640)
+ reverter (35688)
+ routes (35543)
+ routing (35640)
+ tageditor (35640)
+ terracer (35640)
+ turnlanes (35640)
+ turnlanes-tagging (288)
+ undelete (35640)
+ utilsplugin2 (35691)
+ wikipedia (1.1.4)
Tagging presets:
+ ${HOME}/OSM/josmtemplates/xmas/josm_preset.xml
+ ${HOME}/OSM/josmtemplates/Heritage_NRW_preset.xml
+ https://josm.openstreetmap.de/josmfile?page=Presets/Heritage&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Historical_Objects&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/SentieriItaliani&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/NewTags&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/hiking_routes_with_trail_marking&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/PublicTransportOneClick&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Playground_Equipment&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Healthcare&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Crafts&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/WifiHotspots&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/COVID-19&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Healthcare&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Crafts&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Telefonzellen_Deutschland&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/public_bookcase&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/pedestrian_crossings_in_DE&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Radwege&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/StolpersteineLight&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/caravan_site&zip=1
+ https://josm.openstreetmap.de/josmfile?page=Presets/Xmas&zip=1
Map paint styles:
- https://josm.openstreetmap.de/josmfile?page=Styles/Coloured_Streets&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/LayerChecker&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/PublicTransport&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/ShowID&zip=1
- https://www.dropbox.com/s/qo3ai47fpv241jf/Styles_Fixme_and_Notes.zip?raw=1
- https://josm.openstreetmap.de/josmfile?page=Styles/iD&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/Fixme&zip=1
- https://josm.openstreetmap.de/josmfile?page=Styles/HiDPISupport&zip=1
Last errors/warnings:
- 00308,672 W: JCS TMS - error loading object for tile 20/271062/175206@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00309,127 W: JCS TMS - error loading object for tile 20/271062/175207@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00309,636 W: JCS TMS - error loading object for tile 20/271062/175206@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00310,077 W: JCS TMS - error loading object for tile 20/271062/175207@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00310,556 W: JCS TMS - error loading object for tile 20/271062/175206@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00311,044 W: JCS TMS - error loading object for tile 20/271062/175207@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00311,552 W: JCS TMS - error loading object for tile 20/271062/175207@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00312,006 W: JCS TMS - error loading object for tile 20/271062/175206@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00312,500 W: JCS TMS - error loading object for tile 20/271062/175207@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
- 00312,955 W: JCS TMS - error loading object for tile 20/271062/175206@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_gebaeude: Caught exception during read:
Attachments (0)
Change History (12)
comment:1 by , 4 years ago
| Keywords: | performance added |
|---|
comment:2 by , 4 years ago
The changes for #20014 increased the memory needs for the tile cache. It is possible that JOSM requires more memory now. With all those installed plugins, presets and styles you probably use quite a lot of the available 950 MB without doing anything.
comment:3 by , 4 years ago
Memory settings have not been changed (just started with java -jar ... )
All other version before worked with the same settings.
Is there an option to start without plugins etc. to see if these are the problem (due to memory)?
comment:5 by , 4 years ago
New stable JOSM Version (17580) started without Plugins reports: Memory Usage: 745 MB / 950 MB (25 MB allocated, but free)
New stable JOSM Version (17580) started with Plugins reports: Memory Usage: 571 MB / 950 MB (16 MB allocated, but free)
Previous stable JOSM Version (17428) started without Plugins reports: Memory Usage: 760 MB / 950 MB (243 MB allocated, but free)
Previous stable JOSM Version (17428) started with Plugins reports: Memory Usage: 635 MB / 950 MB (89 MB allocated, but free)
All loaded with the same set of Data and background layers - not sure if this helps?
comment:6 by , 4 years ago
Hm, did you mix up the values with/without? IT's not plausible that JOSM requires less memory when plugins are loaded.
comment:7 by , 4 years ago
Pretty sure I did not mix them up as the results puzzled me as well .. but I did another round - this time I closed all programs with potentially variable memory consumption like browser, email before. Result:
New stable JOSM Version (17580) started without Plugins reports: Memory Usage: 672 MB / 950 MB (11 MB allocated, but free)
New stable JOSM Version (17580) started with Plugins reports: Memory Usage: 790 MB / 950 MB (14 MB allocated, but free)
Previous stable JOSM Version (17428) started without Plugins reports: Memory Usage: 450 MB / 950 MB (17 MB allocated, but free)
Previous stable JOSM Version (17428) started with Plugins reports: Memory Usage: 651 MB / 950 MB (115 MB allocated, but free)
The numbers about the tile layer memory allocation in the startup log most likely reflect the change you mentioned before:
New stable JOSM Version (17580) startup: Allocate for tile source layer: 182 MB of memory. Available: 900 MB.
Previous stable JOSM Version (17428) startup: Allocate for tile source layer: 80 MB of memory. Available: 900 MB.
100% increase is of course significant if memory is rare .. but JOSM only ran into trouble for me in the past wirh really big data sets and longer mapping sessions.
BUT:
keeping an eye on the systemmonitor while running 17580 it's not memory that is running out, but CPU usage is maximized while the error logging repeats:
2021-03-26 13:43:21.235 WARNUNG: JCS TMS - error loading object for tile 18/67771/43799@/www.wms.nrw.de: Gebäude Auswahl - adv_alkis_flurstuecke: Caught exception during read:
With 17428 memory consumption is similar (1.3 GB Used of 3.7 GB available), but CPU is acting normal and no error messages occur.
comment:8 by , 4 years ago
Well, you have to monitor the java memory, not the system memory. I use VisualVM for this but there are lots of other tools as well. Or you can simply try to give JOSM more memory with java -Xmx2G -jar ..
comment:9 by , 4 years ago
more memory works - might be worth checking if more people run into the same issue and report the lack of memory in the UI.
comment:11 by , 4 years ago
| Component: | Core → Core imagery |
|---|---|
| Keywords: | memory added |
Can you tell us more precise which versions make a difference, please. See Archiv for older versions. Thanks.
Replying to stephan@…:
Was the memory setting changed? Manually or automatically?
This might indicate one problem.