Modify

Opened 17 years ago

Closed 16 years ago

#1668 closed defect (wontfix)

Memory Leak (1042)

Reported by: c4o88k802@… Owned by: framm
Priority: minor Milestone:
Component: Core Version: latest
Keywords: memory leak Cc:

Description

Did some editing with JOSM which icluded loading trackpoints and yahoo photo overlays. Left the application on (idle) and went to sleep. Next morning I was greeted with out of memory error from Josm.

Lets see if I can attach the java core dump file here.

Attachments (1)

javacore.20081019.040437.28934.0003.txt.zip (53.8 KB ) - added by c4o88k802@… 17 years ago.

Download all attachments as: .zip

Change History (9)

by c4o88k802@…, 17 years ago

comment:1 by anonymous, 17 years ago

Can you modify my email not to be visible for all spambots?

heapdump.20081019.040437.28934.0002.phd.zip (1.2megabytes) available at:

http://d01.megashares.com/?d01=72dd19e

Note the file will be deleted automatically in 5.11.2008 if no downloads are done.
Other wise it will be automatically deleted 5.12.2008

comment:2 by anonymous, 17 years ago

This is reproduceable. Again this morning the same situation. Both crashes have happened few mnutes past 4 am, perhaps a coincidence?

java version "1.6.0"
Java(TM) SE Runtime Environment (build pxi3260sr1-20080416_01(SR1))
IBM J9 VM (build 2.4, J2RE 1.6.0 IBM J9 2.4 Linux x86-32 jvmxi3260-20080415_18762 (JIT enabled, AOT enabled)
J9VM - 20080415_018762_lHdSMr
JIT - r9_20080415_1520
GC - 20080415_AA)
JCL - 20080412_01

comment:3 by JohannesRudolph, 17 years ago

Perhaps you could use the switch -XX:+HeapDumpOnOutOfMemoryError when starting josm and then upload the memory dump once it happens again.

comment:4 by anonymous, 17 years ago

http://d01.megashares.com/?d01=8ba016b
this one generated with version 1056.
Strange though that this dump also happened just after 4 am. I wonder if it's a coincidence or something causing it. next time I'll start JOSM at 3 am and see.

comment:5 by anonymous, 17 years ago

I started JOSM at 03:17 and again, it run out of memory at about 4am. I'm starting to believe it has something to do with my system and not with JOSM.

Lookng at /var/log/messages.* and there seems to be task run at the time this problem occurs, namely gconfd. I'll try to find out what's the deal with these tasks. I don't think this is a bug in JOSM.

comment:6 by anonymous, 16 years ago

Found the reason, not gconfd.
There is a nightly task which checks the computer if there is anonymous ftp service available in any of the open ports accepting connections. That task connects to YWMS port and apparently YWMS doesn't like the input and it reserves all the available memory.

comment:7 by anonymous, 16 years ago

I'm not sure if this is JOSM bug or bug in the plugin.

Connect to port 8000 (the port YWMS is listening).
Once connected, close the connection without sending anything.
Wait some seconds as JOSM starts to eat up all memory.

comment:8 by stoecker, 16 years ago

Resolution: wontfix
Status: newclosed

YWMS is no longer required. Closing.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain framm.
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.