#2620: Exception when initializing large repo
-------------------------------+--------------------------------------------
Reporter: [EMAIL PROTECTED] | Owner: daniel
Type: defect | Status: new
Priority: normal | Milestone:
Component: trac-admin | Version: 0.9.3
Severity: major | Resolution:
Keywords: |
-------------------------------+--------------------------------------------
Comment (by [EMAIL PROTECTED]):
Correct. The memory usage is over 2GB, even with the patch applied, and
the whole process
crash when that limit is reached.
The db initialization does not stop at the same revision every time. We
reach to about
revision 46000 and the the whole thing ends with the above exception. (+-
10-20 revisons)
I really think our repo is in mint condition and that it is the memory
usage
(oom killer is not far off) that is the culprit. I'll try out the script
anyway.
Note that this is a 32bit box with 5GB of RAM.
I will reverify that I have applied the patch correctly and that it is in
use when doing the
initialization, but I do belive this is the case.
Do you know of others with similarly large repos that use trac?
--
Ticket URL: <http://projects.edgewall.com/trac/ticket/2620>
The Trac Project <http://trac.edgewall.com/>
_______________________________________________
Trac-Tickets mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac-tickets
