Modify ↓
Opened 9 years ago
Last modified 4 years ago
#11481 assigned defect
JOSM freezes for some time on slow Internet connection
Reported by: | anonymous | Owned by: | wiktorn |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core imagery | Version: | latest |
Keywords: | wms connection download progress | Cc: |
Description
What steps will reproduce the problem?
- Open Imagery -> Configuration - JOSM freezes for some time <30s
- Refresh list of available imageries - JOSM freezes for long time <1m
- Select WMS type endpoint from Imagery list and wait for layers list - JOSM freezes, sometimes for a long time, one time I must kill it (timeout?)
What is the expected result?
Downloading dialog or status bar with button to cancel
Please provide any additional information below. Attach a screenshot if possible.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2015-05-25 01:32:15 Last Changed Author: wiktorn Revision: 8425 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Relative URL: ^/trunk URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2015-05-24 23:41:24 +0200 (Sun, 24 May 2015) Last Changed Rev: 8425 Identification: JOSM/1.5 (8425 pl) Linux Ubuntu 14.04.2 LTS Memory Usage: 382 MB / 869 MB (287 MB allocated, but free) Java version: 1.7.0_79, Oracle Corporation, OpenJDK 64-Bit Server VM Java package: openjdk-7-jre:amd64-7u79-2.5.5-0ubuntu0.14.04.2 Plugins: - OpeningHoursEditor (30962) - PicLayer (31114) - editgpx (30892) - geotools (31068) - jts (31002) - opendata (31116) - photo_geotagging (30967) - photoadjust (30964) - reverter (31120) - tag2link (31066) - utilsplugin2 (31120)
Attachments (0)
Change History (3)
comment:1 by , 9 years ago
Component: | Core → Core imagery |
---|---|
Keywords: | wms added; template_report removed |
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 9 years ago
Note:
See TracTickets
for help on using tickets.
First point was fixed in [8750].
Refresh list of available imageries needs bigger refactoring of
ImageryLayerInfo.loadDefaults()
so when it's called in initialization it will not show progress bar, when it is called from other places - it will show the progress bar.