diff options
Diffstat (limited to 'open_issues/exec_memory_leaks.mdwn')
| -rw-r--r-- | open_issues/exec_memory_leaks.mdwn | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/open_issues/exec_memory_leaks.mdwn b/open_issues/exec_memory_leaks.mdwn index 67281bdc..1fc5a928 100644 --- a/open_issues/exec_memory_leaks.mdwn +++ b/open_issues/exec_memory_leaks.mdwn @@ -94,3 +94,28 @@ After running the libtool testsuite for some time: 8 39.5 0:15.60 28:48.57 9 0.0 0:04.49 10:24.12 10 12.8 0:08.84 19:34.45 + + +# IRC, freenode, #hurd, 2013-10-08 + + * braunr hunting the exec leak + <braunr> and i think i found it + <braunr> yes :> + <braunr> testing a bit more and committing the fix later tonight + <braunr> pinotree: i've been building glibc for 40 mins and exec is still + consuming around 1m memory + <pinotree> wow nice + <pinotree> i've been noticing exec leaking quite some time ago, then forgot + to pay more attention to that + <braunr> it's been more annoying since darnassus provides web access to + cgis + <braunr> automated tools make requests every seconds + <braunr> the leak occurred when starting a shell script or using system() + <braunr> youpi: not sure you saw it, i fixed the exec leak + + +## IRC, freenode, #hurd, 2013-10-10 + + <gg0> braunr: http://postimg.org/image/jd764wfpp/ + <braunr> exec 797M + <braunr> this should be fixed with the release of the next hurd packages |