- in the lower right corner of jEdit you can see the actual memory consumption of jEdit, like 22/84MB. That means 84MB is reserved for Java, but only 22MB is used currently. Reporting that would be useful. Also try to double-click on that, thus forcing a garbage collection. The maximum usage of memory should remain below 128MB, even if you open the Regression tests or some big doc file from the help. If the garbage collection doesn't reduce the used memory, then there is a memory leak, which I have to fix.
- "Closing jEdit does not recover any memory." That's perhaps because you installed the jEdit server, which runs in the background, so the jedit.bat file (for running jedit) contains the -background or -server option.
Bert
Nick Payne írta:
-----Original Message----- Behalf Of Valentin Villenave Sent: Saturday, 3 January 2009 05:38 To: Bertalan Fodor Cc: lilypond-user Mailinglist Subject: Re: LilyPondTool-2.12-r1 for download [snip] About the memory problem: I'll do some benchmarking when I have more time.I noticed while using the new LPT yesterday that when I initially start jEdit and load the ly file I am currently working on, javaw.exe is using about 83Mb of memory. After about 20 minutes of work on the file memory use has increased to ~120Mb, and after a couple of hours it is at ~220Mb. Closing jEdit does not recover any memory. This is on Windows with the latest JRE from Sun and jEdit 4.3pre16. I have also noticed a problem with the jPedal display of the PDF output. See attached png. Both the harmonic indications have a dashed line, and both lines appear dashed when the file is opened in Acrobat, but jPedal shows the lower line as solid. Nick
_______________________________________________ lilypond-user mailing list address@hidden http://lists.gnu.org/mailman/listinfo/lilypond-user
