Opened 14 years ago
Closed 13 years ago
#7485 closed defect (fixed)
upload dialog: typing a comment is slow due to high cpu load
| Reported by: | Cobra | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
Typing a changeset comment is very slow, during typing a lot of cpu time is consumed.
Something must be triggered in the background.
Version: r5047
Attachments (0)
Change History (7)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
This happens when editing in densely mapped areas or large areas.
I noticed that for every character typed, a way gets unhighlighted and highlighted again (like it happens when moving the cursor over it). I did not see this every time, but every time I could see it, that lag was present.
I could figure out a way to reproduce this for me:
- download some densely mapped area
- change something
- move the cursor over a complex way (e.g. landuse=residential with many nodes) so it gets highlighted (and notice there is a slight lag doing so)
- open the upload dialog via shortkey (it will also happen when using the button, but this is unreliable)
- type fast
Monitoring cpu usage at low intervals (I've got 50ms resolution) helps to see that something is going on.
Java version: 1.6.0_30, Sun Microsystems Inc., Java HotSpot(TM) 64-Bit Server VM, ubuntu 10.10
comment:3 by , 14 years ago
I can get the CPU usage up using the way Cobra described (from 40% to 100%). No idea to what’s the cause, though.
comment:4 by , 14 years ago
Each key press in upload dialog cause repaint of layer... I am debugging.
comment:5 by , 14 years ago
It is not specific for upload dialog. Keypress in every dialog - add property, F12 preferences, etc. (but not in main window) leads to map repaint.
Thank you for noticing such big waste of CPU!
follow-up: 7 comment:6 by , 13 years ago
Do you still observe this behaviour ? I cannot reproduce with latest.
comment:7 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Replying to Don-vip:
I cannot reproduce with latest.
Me neither. Seems like this has been fixed by now.



How to reproduce it? (I can not) Does it depend on OS or OSM file?