Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 348312 - BlameGenerator doesn't release RevWalk graph
Summary: BlameGenerator doesn't release RevWalk graph
Status: NEW
Alias: None
Product: JGit
Classification: Technology
Component: JGit (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-04 19:47 EDT by Shawn Pearce CLA
Modified: 2011-06-04 19:47 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Shawn Pearce CLA 2011-06-04 19:47:58 EDT 
The results from the BlameGenerator leaves all of the parent pointers fully connected. If a source file has existed since the root commit of the project, but isn't modified often (e.g. a top level README) the RevCommits returned by the BlameGenerator will hold onto the entire project history in memory. This is expensive.

The BlameGenerator should cut the history graph down by rewriting the parent pointers similar to what the PathFilter does when its attached to a RevWalk.