Opened 15 years ago
Last modified 13 years ago
#5971 closed defect
WMS-Plugin memory-leak — at Version 3
| Reported by: | Bürste | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | tested |
| Keywords: | imagery wms bing memoryleak | Cc: | Upliner |
Description (last modified by )
When using WMS Plugin I ran every time out of memory.
Memory usage as Private Bytes according Process Explorer.
Reproduce:
-Open JOSM via Webstart. Memory usage: 115M
-Load OSM Data, best for testing is a hugh dataset. 180M
-Open Bing Layer 187M
-Zoom in 188M
-Scroll 1 Minute 326M
-Scroll another Minute 336M
-Close Layer, Open next Bing Layer 337M
-Scroll 1 Minute (with degraded performance) 360M
-Close Layer, Open next Bing Layer 361M
-Load some additionally OSM Data and now JOSM is nearly completly unusable 361M
If you now would use it further its only a question of time when it would run completly out of memory.
Change History (3)
comment:1 by , 15 years ago
| Cc: | added |
|---|
comment:2 by , 15 years ago
comment:3 by , 15 years ago
| Component: | Core imagery → Core |
|---|---|
| Description: | modified (diff) |
| Keywords: | imagery wms bing memoryleak added |
| Priority: | major → normal |
Note:
See TracTickets
for help on using tickets.
I second this, recently there've been a lot of OutOfMemoryErrors after using Bing layer. I'm experiencing one right now, spiced up by "Autosafe failed" messages in the console.