Ticket #76 (closed: fixed)
Revision Graph Doesn't Work
| Reported by: | cwaig | Owned by: | alwin |
|---|---|---|---|
| Priority: | normal | Milestone: | 0.8.x |
| Component: | All | Version: | 0.8.x |
| Severity: | minor | Keywords: | RESOLVED |
| Cc: |
Description
This seems to be a slightly different failure mode to report #74 - on selecting the "Full Revision Tree" option, kdesvn starts using all available memory - the graph is never displayed and I had to kill kdesvn when memory usage topped the 1G mark.
This is with a fairly large project, with several hundred source files.
Attachments
Change History
comment:1 Changed 7 years ago by cwaig
- Owner changed from anonymous to alwin
- Status changed from new to assigned
comment:2 Changed 7 years ago by alwin
Yes. Known problem. I'm working hard for a solution. The reason behind:
Subversion stores information about copy/move operations as "coming from" not "going to". That means: I had to download ALL logentries. and parse them twice:
- rewrite all copy/move internal from "coming from" to "going to", eg. forward references.
- second stage is checking the origin of selected element. eg, follow ALL nodes, check if the changelist contains the item selected and so on.
That consumes a lot of memory and sometimes a lot of CPU. For instance for the kde-repository itself it is impossible to use :(
If someone have nice idea how to reduce that - tell me. But I think as long as subversion will not have a full log about a specific element, eg, doing on serverside what I have to do on client side this moment nothin will work :(
Real sorry about that. Real sorry. I use that tree myself in large projects, and I saw the limit myself more than once.
