WMS plugin huge memory leakage

[bilbo]

After running JOSM for some (quite long) time, Yahoo WMS stopped working and I got these repeating messages in console:

Grabbing HTML http://josm.openstreetmap.de/wmsplugin/YahooDirect.html?bbox=14.5870164,50.1124421,14.5905298,50.1146952&srs=EPSG:4326&width=570&height=570
java.io.IOException: Could not start browser. Please check that the executable path is correct.
Cannot run program "webkit-image": java.io.IOException: error=12, Cannot allocate memory
        at wmsplugin.HTMLGrabber.grab(HTMLGrabber.java:44)
        at wmsplugin.WMSGrabber.fetch(WMSGrabber.java:68)
        at wmsplugin.Grabber.attempt(Grabber.java:82)
        at wmsplugin.WMSGrabber.run(WMSGrabber.java:51)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
        at java.lang.Thread.run(Thread.java:619)

I run JOSM with -Xmx1024m and I have still enough of free RAM when this started to happen.

When this happened, I had only three GPX layers (containing only about 100 waypoints total and no tracks), one quite small OSM layer (about 200 Kb of data when saved) and two other WMS layers opened (these were quite heavily used, so maybe the leaked memory was because of them). When I added third (Yahoo) layer, WMS plugin loaded about 6 or 7 images and then started throwing this exception.

Even deleting the other WMS layers does not free any memory. Strange thing is, that I can still edit without any problems. Deleting Yahoo layer and then re-adding it does not help either. Deleting WMS cache (~ 5000 files, 200 MB) also have no effect.

Other WMS (ordinary WMS's) still work.

[jttt]

It's not mentioned in the track but I suppose you're using open-jdk, see ​this link for details.

Closing as it's probably a bug in open-jdk.