[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jgit-dev] How to deal with LargeObjectException in RevWalk.parseCommit?
|
One of our users is running into a LargeObjectException$ExceedsLimit for
RevWalk.parseCommit. I'm not sure what can make a commit-object itself
that large, but I'm wondering if it's reasonable to have a limit here at
all? Personally, I'd prefer to let the application run into an OOME
here. Should we make the limit configurable by a system property?
org.eclipse.jgit.errors.LargeObjectException$ExceedsLimit: Object
8260e144113486b44c81bed39eb10dedd834804c exceeds 5 242 880 limit, actual
size is 26 693 640
at org.eclipse.jgit.lib.ObjectLoader.getCachedBytes(ObjectLoader.java:191)
at org.eclipse.jgit.revwalk.RevWalk.getCachedBytes(RevWalk.java:861)
at org.eclipse.jgit.revwalk.RevWalk.parseNew(RevWalk.java:825)
at org.eclipse.jgit.revwalk.RevWalk.parseAny(RevWalk.java:811)
at org.eclipse.jgit.revwalk.RevWalk.parseCommit(RevWalk.java:724)
at smartgit.hU.a(SourceFile:220)
at smartgit.hU.a(SourceFile:201)
at smartgit.gJ.a(SourceFile:333)
at smartgit.gJ.a(SourceFile:237)
at smartgit.gJ.a(SourceFile:61)
at smartgit.axQ.a(SourceFile:143)
at smartgit.axQ.b(SourceFile:65)
at smartgit.ayK.run(SourceFile:46)
-Marc
