Community
Participate
Working Groups
Version: 0.7.9.I20110207-1700 SVN Client: org.eclipse.team.svn.connector.svnkit15 2.2.2.I20110124-1700 SVN/1.5.6 SVNKit/1.2.3 (http://svnkit.com/) r5745 JVM Properties: {java.runtime.name=Java(TM) SE Runtime Environment, java.runtime.version=1.6.0_24-b07-334-10M3326, java.vendor=Apple Inc., line.separator= , java.class.version=50.0, os.name=Mac OS X, os.arch=x86_64, user.country=US, os.version=10.6.7, eclipse.commands=-os macosx -ws cocoa -arch x86_64 -showsplash -launcher /Applications/eclipse/Eclipse.app/Contents/MacOS/eclipse -name Eclipse --launcher.library /Applications/eclipse/Eclipse.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher.cocoa.macosx.x86_64_1.1.2.R36x_v20101019_1345/eclipse_1310.so -startup /Applications/eclipse/Eclipse.app/Contents/MacOS//../../../plugins/org.eclipse.equinox.launcher_1.1.1.R36x_v20101122_1400.jar -product org.eclipse.epp.package.php.product -keyring /Users/shannonwarren/.eclipse_keyring -showlocation -vm /System/Library/Frameworks/JavaVM.framework , java.version=1.6.0_24, osgi.framework.version=3.6.2.R36x_v20110210, file.separator=/, java.vm.info=mixed mode, path.separator=:, user.timezone=America/Chicago, user.language=en, java.vm.name=Java HotSpot(TM) 64-Bit Server VM, file.encoding=MacRoman} java.lang.OutOfMemoryError: Java heap space
*** Bug 349594 has been marked as a duplicate of this bug. ***
*** Bug 349595 has been marked as a duplicate of this bug. ***
There is not much information in the report, so the real cause of the OutOfMemoryError could be anywhere (and not in the Subversive actually). The only thing I could pinpoint from this report is that you're still using SVN Kit 1.2.3-based connector and this SVN Kit version is known to have memory leaks. So, in order to exclude this from equation you could use SVNKit 1.3.5-based one instead. On the other hand when "out of memory" error is caused by older version of SVN Kit it looks differently in the report all the time and so, it will be reasonable to check other plug-ins (if you had any) as possible sources of memory leaks too.