Changes between Initial Version and Version 1 of Ticket #5331, comment 12


Ignore:
Timestamp:
2012-03-23T02:57:21+01:00 (14 years ago)
Author:
xeen

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #5331, comment 12

    initial v1  
    11I can reproduce the problem. Adding data.clear() to OsmDataLayer.java#destroy helps: Java then reports that more of the heap is free ("allocated, but free" in JOSM’s status report).
    22
    3 Analyzing the heap dumps using Eclipse’s MAT gives about the same results: If data.clear is called is heap is around 60 MB with top consumers being ImageCaches in swing.….GTKEngine and bufferedImages in MapView (so MapView seems to leak as well; at least I believe it is destroyed when there are no more layers.).
     3Analyzing the heap dumps using Eclipse’s MAT gives about the same results: If data.clear is called the heap is around 60 MB with top consumers being ImageCaches in swing.….GTKEngine and bufferedImages in MapView (so MapView seems to leak as well; at least I believe it is destroyed when there are no more layers.).
    44
    55Without data clear the heap uses 320 MB of which 280 belong to DataSet. The follow-ups are again GTKEngine and bufImgs in MapView.