Hello,
I've Debuged my Problem further.
With the Function getLogMessages in the Interface ISVNClientAdapter and all
of its implementations, the Log message are fetch with the svn-argument -v.
This means, that to all LogMessage the affected Paths are loaded. In a large
or very long repository this can produce a OutOfMemory Exception and very
long waiting time. The Question is, is it really neccassary to load all the
information to all Log messages at this time.
Is there no possibility to load the affected Paths on Demand? So less trafic
is produced and the waiting times for a result are much shorter, if the
application
loads only the affected Paths, which I will see on the screen.
Thanks in advance
regards
Klaus Akin
-----Ursprüngliche Nachricht-----
Von: Akin, Klaus [mailto:Klaus.Akin@infor.de]
Gesendet: Dienstag, 15. März 2005 10:54
An: users@subclipse.tigris.org
Betreff: Show in revision history ran out of Memory
Hello,
When i let Subclipse show the inital history in the SVN Repository
Perspective i get a Java out of memory exception.
if I let the information be printed in a File with the command svn log -v it
works, but the file has about 25MB. Is there a memory leak in Subclipse. On
my machine
the corresponding javaw process ran to 94MB and the Exception is occoring.
Here is the log Massege of eclipse:
!SESSION Mrz 15, 2005 10:41:03.231
---------------------------------------------
eclipse.buildId=M200409161125
java.version=1.4.2_02
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=de_DE
Command-line arguments: -vmarg -Xmx 700M
!ENTRY org.eclipse.ui 4 4 Mrz 15, 2005 10:41:03.231
!MESSAGE Unhandled event loop exception
!ENTRY org.eclipse.ui 4 0 Mrz 15, 2005 10:41:03.261
!MESSAGE java.lang.OutOfMemoryError
!STACK 0
java.lang.OutOfMemoryError
!ENTRY org.eclipse.core.runtime 4 2 Mrz 15, 2005 10:41:03.272
!MESSAGE An internal error occurred during: "Fetching SVN revision history".
!STACK 0
java.lang.OutOfMemoryError
Thanks in advance
Regards
klaus akin
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
###########################################
This message has been scanned by F-Secure Anti-Virus for Microsoft Exchange.
For more information, connect to http://www.F-Secure.com/
Received on Thu Mar 17 21:27:37 2005