Opened 21 months ago
Closed 21 months ago
#23554 closed defect (irreproducible)
Validation Results panel lags for 20+ second after deleting a building when I have 400+ validation warnings
| Reported by: | anonymous | Owned by: | anonymous |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | Cc: |
Description
To reproduce this:
- download area with a 400-800 houses
- select them all by searching for "building:"
- copy and paste them and then move them so that they all overlap
- open Validation and click Validate, you should see hundreds of building overlap warnings
- open the "Overlapping buildings" warnings drop down in the Validation Results panel - I see a spinning beachball for 20 seconds when I do this
- select just one of the buildings and delete it
What I expect:
The building is deleted quickly
What actually happens:
The building is deleted quickly, but then I get a loading spinner for 20 seconds or so where I can't use JOSM at all. For each building. Closing the Overlapping buildings dropdown I can delete buildings quickly without the delay again.
It seems like deleting the actual building is fast but it's doing something else after. I can delete 100s of building at once and the deletion is quick and the amount of delay is the same. There's also a very noticeable switch where deleting becomes fast again once you get down to about 200-400 warnings. It seems like there's some kind of quadratic algorithm somewhere in the dropdown cod of the Validator panel.
I'm on an M1 Macbook Air with 8GB of RAM and JOSM is using 7.1GB of it.
Attachments (0)
Change History (3)
comment:1 by , 21 months ago
comment:2 by , 21 months ago
| Owner: | changed from to |
|---|---|
| Status: | new → needinfo |
What area do you download?
I've tried with +6000 overlapping buildings and see no performance problem. It might be caused by a mappaint style or a preference setting or just too much other data. I see no reason why JOSM should use 7.1GB memory for this small number of buildings, so maybe the area contains a huge amount of other data?
comment:3 by , 21 months ago
| Resolution: | → irreproducible |
|---|---|
| Status: | needinfo → closed |
I can't reproduce it anymore either.



I cannot reproduce this with tested version r19017 on Windows. If you use the same version please attach the status report. See below for the details.
Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.
Please add all needed information according to this list:
To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help →
Report Bug.
Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!