Modify

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#8919 closed defect (fixed)

Out of Memory Exception

Reported by: pinkduck Owned by: team
Priority: normal Milestone:
Component: unspecified Version: tested
Keywords: memory, hprof, crash Cc:

Description (last modified by Don-vip)

JOSM 6060 is crashing for me after around 17–20 edit sessions using Bing and OS StreetView background tiles. I have uploaded a zip file of an .hprof file created by "-XX:+HeapDumpOnOutOfMemoryError” option in the hope that the cause can be identified and resolved so that I don’t need to manually stop and restart the editor too often. I run JOSM with command line " -Xmx512M”.

http://sdrv.ms/1e69JJq

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2013-07-10 01:34:22
Last Changed Author: stoecker
Revision: 6060
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2013-07-08 22:13:24 +0200 (Mon, 08 Jul 2013)
Last Changed Rev: 6060

Identification: JOSM/1.5 (6060 en_GB) Windows 7 64-Bit
Memory Usage: 163 MB / 455 MB (111 MB allocated, but free)
Java version: 1.7.0_25, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
VM arguments: [-Xmx512M, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=C:\Users\Pink Duck\Downloads\JOSM.hprof]

Plugin: reverter (29663)
Plugin: undelete (29555)

Attachments (1)

Status.txt (44.0 KB ) - added by pinkduck 12 years ago.
JOSM Status Report

Download all attachments as: .zip

Change History (10)

comment:1 by pinkduck, 12 years ago

Description: modified (diff)

comment:2 by pinkduck, 12 years ago

Description: modified (diff)

comment:3 by rickmastfan67, 12 years ago

Might want to bump up the memory you give JOSM. That "-Xmx512M" is very low and odds are, causing your problem.

Try boosting that to "-Xmx1024M" if you have enough ram on your computer and see what happens. ;)

comment:4 by pinkduck, 12 years ago

That’s a workaround, but the actual problem is that memory after use is not being properly released. There's a bug somewhere there to fix, which could be analysed by looking at whatever the significant number of similar type objects are in the .hprof profile.

comment:5 by Don-vip, 12 years ago

Can you please post your status info ? Knowing the list of plugins installed on your machine is important in memory leaks hunting.

by pinkduck, 12 years ago

Attachment: Status.txt added

JOSM Status Report

comment:6 by Don-vip, 12 years ago

Description: modified (diff)

comment:7 by Don-vip, 12 years ago

Resolution: fixed
Status: newclosed

In 6107/josm:

fix #8919 - fix memory leaks, including one introduced with r5982

comment:8 by bastiK, 12 years ago

Nice, what tools did you use to find the leaks?

comment:9 by Don-vip, 12 years ago

Jvisualvm:

  • load hprof
  • compute 20 largest objects by retained size
  • open first instance and look for references
  • right click: get nearest GC root

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.