Overview
| Artifact ID: | e932f8a1d2ec0949273727ef273413944055bf99 |
|---|---|
| Ticket: | 708eab9d48592746b30974c580d353c777c8c609
Message "killed" opening large repository |
| User & Date: | anonymous 2010-01-14 17:45:20 |
Changes
- Appended to comment:
<hr><i>anonymous added on 2010-01-14 17:45:20:</i><br> I just reran the test, first copying the SVN repository over and removing all '.svn' directories. Then I created a repo "fossil new t", changed dir to the interesting dir and "fossil open ../t; fossil add *; fossil ci -m 'test'" Then I created another directory, and did "fossil open ../t" there. The result is the same: a "Killed" message. However, something interesting: I ran "top" in another window, and saw the memory usage of fossil go upwards of 1.5G before it was finally killed. So I think the problem is there is a (bad) memory leak in the "open" scenario (and perhaps generally). For I cannot see any reason for the memory usage to ramp up so high. I also did "find . -type f | wc" in that dir, the result is 52,218. The fossil rstats reported 51,192 files ... I'm not sure what the discrepancy would be besides the _FOSSIL_ and two manifest files.