﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
17040	Memory leaks	GerdP	team	"==== What steps will reproduce the problem?
1. Download OSM data
2. Press Ctrl+H to see history of a selected object
3. Close all data layers
4. Use VisualVM to create a heapdump after a GC

==== What is the expected result?
No instances of VersionInfoPanel 
==== What happens instead?
Some instances of this class, also various other instances of josm.gui.history.*
==== Please provide any additional information below. Attach a screenshot if possible.
{{{
Build-Date:2018-11-26 18:47:05
Revision:14455
Is-Local-Build:true

Identification: JOSM/1.5 (14455 SVN en) Windows 10 64-Bit
OS Build number: Windows 10 Home 1803 (17134)
Memory Usage: 4871 MB / 5461 MB (4694 MB allocated, but free)
Java version: 1.8.0_191-b12, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Screen: \Display0 1920x1080
Maximum Screen Size: 1920x1080

Plugins:
+ FastDraw (34510)
+ apache-commons (34506)
+ buildings_tools (34724)
+ download_along (34503)
+ editgpx (34737)
+ ejml (34389)
+ geotools (34513)
+ gpxfilter (34506)
+ jaxb (34506)
+ jts (34524)
+ measurement (34529)
+ o5m (34405)
+ opendata (34698)
+ pbf (34576)
+ poly (34546)
+ reverter (34552)
+ utilsplugin2 (34506)

Map paint styles:
- https://josm.openstreetmap.de/josmfile?page=Styles/Lane_and_Road_Attributes&zip=1

Last errors/warnings:
- W: No configuration settings found.  Using hardcoded default values for all pools.
}}}
"	defect	closed	normal	18.12	Core		fixed	template_report memory	skyper
