0000375: Java heap space during check out

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0000375

[SVNKit] bug

major

always

2010-06-09 13:04

2010-07-14 11:26

Reporter

Igor Burilo

View Status

public

Assigned To

oka

Priority

normal

Resolution

open

Status

assigned

Product Version

1.3.x

Summary

0000375: Java heap space during check out

Description

Problem happens during check out. Then I increased heap space from 256 to 512 Mb in Eclipse. When I observed checking out progress, OutOfMemoryError happened when I had about 200Mb free. Also when I switched to JavaHL it checked out successfully. Project which I checked out had many refactorings and it doesn't contain very big files.

java.lang.OutOfMemoryError: Java heap space
at com.sun.org.apache.xerces.internal.util.XMLStringBuffer.append(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.refresh(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.invokeListeners(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLEntityScanner.peekChar(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(Unknown Source)
at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(Unknown Source)
at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:754)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.readData(HTTPConnection.java:719)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPRequest.dispatch(HTTPRequest.java:216)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:349)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:275)
at org.tmatesoft.svn.core.internal.io.dav.http.HTTPConnection.request(HTTPConnection.java:263)
at org.tmatesoft.svn.core.internal.io.dav.DAVConnection.doReport(DAVConnection.java:266)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.runReport(DAVRepository.java:1261)
at org.tmatesoft.svn.core.internal.io.dav.DAVRepository.update(DAVRepository.java:818)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.update(SVNUpdateClient.java:558)
at org.tmatesoft.svn.core.wc.SVNUpdateClient.doCheckout(SVNUpdateClient.java:914)
at org.tmatesoft.svn.core.javahl.SVNClientImpl.checkout(SVNClientImpl.java:2047)

Additional Information

SVNKit 1.3.2 r6267

Tags

No tags attached.

planned for version

1.2.x

Attached Files

Relationships

Notes
(0000864) oka (administrator) 2010-07-12 18:12	Hello Igor, Please try the same check out operation with SVNKit-based command line client. It works fine even with -Xmx32M heap limit, and in general SVNKit allocate only limited amount of memory. The reason for OOME is probably some other part of Eclipse (it could be event handler for instance) that allocates memory during checking out or independently.

(0000865) Igor Burilo (reporter) 2010-07-14 11:26	I can't reproduce this problem now even with SVNKit 1.3.2. I'll provide more details if it happens again.

Issue History
Date Modified	Username	Field	Change
2010-06-09 13:04	Igor Burilo	New Issue
2010-06-21 13:25	oka	Status	new => assigned
2010-06-21 13:25	oka	Assigned To	=> oka
2010-07-12 18:12	oka	Note Added: 0000864
2010-07-14 11:26	Igor Burilo	Note Added: 0000865

Mantis 1.1.0[^]