Modify ↓
Opened 2 years ago
Closed 8 months ago
#5971 closed defect (duplicate)
WMS-Plugin memory-leak
| Reported by: | Buerste | Owned by: | Buerste |
|---|---|---|---|
| Priority: | normal | Component: | Core |
| Version: | tested | Keywords: | imagery wms bing memoryleak |
| Cc: | Upliner |
Description (last modified by stoecker)
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.
Attachments (0)
Change History (8)
comment:1 Changed 2 years ago by Upliner
- Cc Upliner added
comment:2 Changed 2 years ago by Zverikk
comment:3 Changed 2 years ago by Buerste
- Component changed from Core imagery to Core
- Description modified (diff)
- Keywords imagery wms bing memoryleak added
- Priority changed from major to normal
comment:4 Changed 2 years ago by Buerste
- Description modified (diff)
comment:5 Changed 9 months ago by skyper
What is the status of this ticket ?
comment:6 Changed 9 months ago by stoecker
- Description modified (diff)
- Owner changed from team to Buerste
- Status changed from new to needinfo
comment:7 Changed 8 months ago by skyper
See also #7980
comment:8 Changed 8 months ago by stoecker
- Resolution set to duplicate
- Status changed from needinfo to closed
Closed as duplicate of #7980.
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.