[ jEdit-devel ] [ jedit-Bugs-1359184 ] Memory usage very high

[SourceForge.net <no...@so...>]

Bugs item #1359184, was opened at 2005-11-17 19:31
Message generated for change (Settings changed) made by kerik-sf
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1359184&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: editor core
Group: None
>Status: Pending
>Resolution: Out of Date
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: Memory usage very high

Initial Comment:
I've been using Jedit for several years now and just 
recently had a problem with the editor freezing on 
startup. The activity log indicated an out of memory 
error. I increased the Java heap size using -Xms512m -
Xmx512m and this got the editor started. However, 
when I checked the memory usage on my Windows XP 
machine it was up to 680MB and was everything was 
running really slowly. I rebooted a couple of times 
and the result was the same. 

Not being an expert on the Jedit internals I checked 
my .jedit folder and noticed two large files 
perspective.xml (49MB) and recent.xml (16MB). I 
deleted them and restarted Jedit. The memory usage 
went down to 280 MB (still pretty high) but my 
machine was no longer slow.

I have no idea if this is a bug or just my 
configuration.

Thanks,
Richard

ric...@gm...

----------------------------------------------------------------------

>Comment By: Eric Le Lay (kerik-sf)
Date: 2010-03-22 20:48

Message:
I think that it's too late to investigate


----------------------------------------------------------------------

Comment By: Blackwell (blackweli)
Date: 2005-11-17 20:05

Message:
Logged In: YES 
user_id=971109

If you configure the max. memory limit of the JVM to 512 MB,
expect it to use that eventually. Depending on the JVM
configuration it may not feel urged to start collecting
unused objects (to free up memory) until it reaches those
512 MB. This is a general issue with Java programs/the
standard JVM and is not too much related to jEdit. (Although
one can argue that Java applications can try to minimize
resource usage.)

The XML file issue you mentioned does still look bogus and
worthwhile investigating.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100588&aid=1359184&group_id=588