Opened 3 years ago
Closed 2 years ago
#4778 closed defect (fixed)
Memory Leak
| Reported by: | delta_foxtrot2 | Owned by: | framm |
|---|---|---|---|
| Priority: | normal | Component: | Core imagery |
| Version: | tested | Keywords: | |
| Cc: |
Description
I think there is a memory leak in the slippymap plugin, after heavy use of Nearmap imagery I have to periodically restart JOSM otherwise it crashes or throws up out of memory warnings.
Attachments (0)
Change History (4)
comment:1 Changed 3 years ago by hansendc
- Owner changed from framm to delta_foxtrot2
- Status changed from new to needinfo
comment:2 Changed 3 years ago by delta_foxtrot2
There is no one set of co-ords that trigger this, you just have to use the slippymap plugin for a few hours, the more memory you allocate to JOSM/JAVA the longer it takes to run out of memory.
It doesn't seem to make much difference if you right click and tell JOSM to 'Flush Tile Cache' the problem will still occur, the only known work around is to periodically restart JOSM.
Feel free to vectorise from Nearmap imagery to help fix this bug :)
http://wiki.openstreetmap.org/wiki/Nearmap#Current_coverage
comment:3 Changed 3 years ago by stoecker
- Owner changed from delta_foxtrot2 to framm
- Status changed from needinfo to new
comment:4 Changed 2 years ago by stoecker
- Resolution set to fixed
- Status changed from new to closed
Slippymap is in core now.
Could you post the nearmap configuration that you're using, and perhaps an example set of coordinates where you notice this? How long does it take? We may just need to reduce the number of cached tiles. It's possible that the nearmap tiles are larger than I'm used to.