#5193 closed defect (fixed)
josm got very slow recently
| Reported by: | dieterdreist | Owned by: | team |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
there seems to be a bug as JOSM got very slow recently (noticed today, but could be already for say 7 days as I wasn't editing a lot in the past week).
drawing is almost not possible (the point gets added 1-2 seconds after click).
Attachments (0)
Change History (6)
comment:1 by , 14 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
comment:2 by , 14 years ago
I guess it was caused by locking in dataset, when JOSM had to wait for filters to be applied before it could add node. But JOSM wasn't slow on my pc so I'm only guessing.
Please report whether the fix helped.
comment:3 by , 14 years ago
Shouldn't be to hard to make filter apply on changed primitives and referrers/children, only. Not sure it would make a difference, though. On my pc JOSM wasn't slow either.
comment:4 by , 14 years ago
Yes, I started to make filter apply only on changed primitives but then I decided I will rewrite it a bit more. And if drawing was really as bad as dieterdreist describes, it would be better to have locking disabled until rewrite is done.
comment:5 by , 14 years ago
IMHO this was caused by a complex relation due to JOSM bug, where the relation (around 220 members) grew up to 3400 members, all of them duplicates/multiples of the original members. This obviously augmented display complexity tremendously, causing the slow down effect.
(In [3354]) Fix #5193 josm got very slow recently (reverted fix for #5018)