Help > Show Status Report


Displays the status report with useful information for troubleshooting and development.

Tip: starting with JOSM r17637, a status report can also be obtained from the command line using --status-report

To report an error in JOSM or to request a new feature please use always the Report bug form.
It can be invoked in the Help menu or with the source:trunk/resources/images/bug.svg button in this dialog. This includes all needed technical information in the ticket. Bug reports and feature request are called tickets in JOSM.

The status report consists of the following sections:

Section Description Status Report
Bug Report
Required in a
bug report
1 Release JOSM version details Always Always Yes
2 System Operating system, Java, memory usage, screen size and command line options Always Always Yes
3 Dataset consistency Consistency of the current data layer If available If available Yes, if available
4 Plugins Installed Plugins If available If available Yes, if available
5 Tagging presets Installed Presets If available If available Yes, if available
6 Map paint styles Installed Styles If available If available Yes, if available
7 Validator Rules Installed Rules If available If available Yes, if available
8 Last errors/warnings Overview of last shown or hidden code errors/warnings of JOSM If available If available Yes, if available
9 Crash & Stack Detailed info about the last JOSM code error No If available Yes, if available
10 Threads All stack traces No Optional Optional
11 Preferences Current settings Always No No


  • The sections are not numbered in the report.
  • Some may be empty.
  • Section 4–8 each add a title to their paragraph and each line of the paragraph starts with plus + or minus -.
  • Section 9–10 add a title to their paragraphs

1 Release


Relative:URL: ^/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-07-30 12:44:04 +0200 (Thu, 30 Jul 2020)
Build-Date:2020-07-31 01:30:49

2 System

Memory Usage
The first value is the size of the total memory currently used by the Java Virtual Machine (JVM) including JOSM and garbage. The second value is the max. memory the JVM will try to use, a limit can be the -Xmx option. At last, the third value is the free memory in the JVM.


Identification: JOSM/1.5 (16812 en) Linux Arch Linux
Memory Usage: 387 MB / 3844 MB (191 MB allocated, but free)
Java version: 11.0.8+10, N/A, OpenJDK 64-Bit Server VM
Look and Feel: javax.swing.plaf.metal.MetalLookAndFeel
Screen: :0.0 3840x2160 (scaling 1.0x1.0)
Maximum Screen Size: 3840x2160
Best cursor sizes: 16x16 -> 16x16, 32x32 -> 32x32
VM arguments: [-Djosm.home=<josm.pref>]

3 Dataset consistency

Only one line without separation to the System paragraph.


Dataset consistency test: No problems found

8 Last errors/warnings


Last errors/warnings:
- E: java.nio.file.NoSuchFileException: ${HOME}/b.osm
- E: Error - <html>Could not read file 'b.osm'.<br>Error is:<br>${HOME}/b.osm</html>

9 Crash & Stack

Only present after an error in the Report Bug dialog.

10 Threads

Full stack traces of all running threads. Optionally available through check box in Report Bug dialog.

11 Preferences

Not needed in tickets

To protect sensitive data this keys are stripped: username, password, access-token, file-open.history, download.overpass.query and download.overpass.queries.

Back to Help menu
Back to Main menu
Back to Main Help

Last modified 3 years ago Last modified on 2021-03-22T20:25:01+01:00

Attachments (1)

Download all attachments as: .zip

Note: See TracWiki for help on using the wiki.