Opened 17 months ago
Last modified 17 months ago
#23034 new defect
Application freeze and fail to open image
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description
I clicked on an image icon in the map (part of an opened GPS trace), and all of JOSM froze for a while. Then a dialog appeared reporting that I'd hit a bug in JOSM and writing a long stack trace, etc (attached in josm-error-data.txt).
Meanwhile, an error message was shown inline in JOSM's main map window:
IO Exception: file: /home/troels/nobackup/osm/2023-06-29_17-26-48.jpg
/home/troels/nobackup/osm/2023-06-29_17-26-48.jpg
The file path does not exist on the file system.
Afterwards, JOSM could be used again, but trying to open the same image would again temporarily bring JOSM into the bad state. Other images could be opened without errors.
Trying to report the bug via JOSM failed, so here's a bug report opened via the josm.openstreetmap.org web-interface.
JOSM version: 18746.
I'm attaching the related GPX file.
Attachments (2)
Change History (3)
by , 17 months ago
| Attachment: | josm-error-data.txt added |
|---|
by , 17 months ago
| Attachment: | 2023-06-29_17-26-28.gpx added |
|---|
GPX file containing reference to the non-existing file, causing JOSM to partly fail
comment:1 by , 17 months ago
I suggest JOSM be equipped with a more graceful logic for handling files which are seen in the GPX file but which are not available on the file system as suggested by the GPX.
Copy-paste of stack trace etc displayed by JOSM error dialog