Opened 2 years ago
Last modified 2 months ago
#13129 new defect
trac-admin resync leaks memory
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | high | Milestone: | next-stable-1.4.x |
Component: | version control | Version: | 1.2.3 |
Severity: | normal | Keywords: | svn memory |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
I am using a trac installation 1.2.3 version. Was installed via easy_install
subversion-python27 Version: 1.9.7 python27-psycopg2 Version: 2.5.1 subversion Version: 1.9.7
I'm trying to run a resync in our environment. Unfortunately this fails apparently due to running out of memory. The repository our project uses has over 100k revisions, and my estimation is that trac-admin resync leaks about 40 MB of memory per 1000 revisions. But after 90K revisions he used all 8 gigabytes of RAM.
-bash: fork: Cannot allocate memory
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 401 root 20 0 0 0 0 D 8.3 0.0 0:02.91 kswapd0 10228 root 30 10 7804m 7.0g 1168 D 3.6 93.7 11:59.68 trac-admin 9736 postgres 20 0 328m 133m 132m S 0.7 1.7 0:00.56 postmaster
We are using a postgres 9.6 backend.
Attachments (0)
Change History (5)
follow-up: 2 comment:1 by , 2 years ago
Keywords: | resync removed |
---|
comment:2 by , 2 years ago
comment:3 by , 2 years ago
Confirmed. Memory leaks still exists but 50% less.
Is it planned to solve this problem completely? Or it's technically impossible?
comment:4 by , 2 years ago
Thanks for the feedback.
I spent more time to investigate other memory leaks on #13112, however I couldn't find. I guess that Subversion Python bindings has the causes of the memory leaks, but no evidence.
comment:5 by , 9 months ago
Milestone: | next-stable-1.2.x → next-stable-1.4.x |
---|
I think the issue is the same of #13112. Please try to use 1.2-stable or apply [16835] to Trac 1.2.3.