On 11/15/2012 09:22 AM, Iryoung Jeong wrote:
> Hello,
>
> At first, I'd like to say "I'm sorry" if I bothered anyone(because
> someone was already assigned to this bug)
>
> For me, run_tests failed because of out-of-memory(I have only 1G mem VM
> for testing quantum :(
>
> So, after a few hours of investigation, I found some points of leaks
> which make run_tests can run successfully with 1G mem.
>
> With this patch, final memory consumption looks like this.(with Ubuntu
> Precise 64bit)
>
> UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
> xxxx 15613 15607 98 230434 850328 0 15:39 pts/4 00:06:59 python .//run_tests.py
>
> Definitely, it looks like there's more leaks(still more than 800MB), but this can be starting point for others who'd like to dig further.
> (IMHO, this is just tests, so if production code doesn't have leak, this size of memory leak is acceptable... for me :)
>
Hi,
Thank you for trying to address tis. I have taken a look and the patch
does not address the memory utilization. If you run top whilst the tests
are running you will see how the memory is "chewed up"
Thanks
Gary
On 11/15/2012 09:22 AM, Iryoung Jeong wrote:
> Hello,
>
> At first, I'd like to say "I'm sorry" if I bothered anyone(because
> someone was already assigned to this bug)
>
> For me, run_tests failed because of out-of-memory(I have only 1G mem VM
> for testing quantum :(
>
> So, after a few hours of investigation, I found some points of leaks
> which make run_tests can run successfully with 1G mem.
>
> With this patch, final memory consumption looks like this.(with Ubuntu
> Precise 64bit)
>
> UID PID PPID C SZ RSS PSR STIME TTY TIME CMD
> xxxx 15613 15607 98 230434 850328 0 15:39 pts/4 00:06:59 python .//run_tests.py
>
> Definitely, it looks like there's more leaks(still more than 800MB), but this can be starting point for others who'd like to dig further.
> (IMHO, this is just tests, so if production code doesn't have leak, this size of memory leak is acceptable... for me :)
>
Hi,
Thank you for trying to address tis. I have taken a look and the patch
does not address the memory utilization. If you run top whilst the tests
are running you will see how the memory is "chewed up"
Thanks
Gary