[xdebug-general] Re: xdebug 2.0.4 memory leak?

I meant that the memory usage of the apache process would increase and
stay that way, even after the script execution is finished. Since
xdebug.so is loaded into apache, the apache process seems to use a lot
of memory.

If I don't have xdebug installed, the script is executed and the
increase in memory is temporary, so it will go away, when the script
is done.

That's why I thought there might be something wrong.

On a side note, when I execute the script from the command line, the
memory still increases, but then the process dies and the memory is
released.

I understand that apache processes are being reused in pre-fork mode.
So the process is not necessarily killed after each request. However,
if you do not use xdebug.so at all, the memory usage almost stays
constant, whereas when you use xdebug.so, it increases drastically.

This should not be the case, right?

2009/3/17 Paul Shoemaker <paul.shoemaker[@]helloecho.com>:
> Personally, I am running 2.1.0-dev and am not experiencing any memory
> problems.
>
> What do you mean by "memory gets exhausted"? All available memory in your
> system gets used by that one snippet when tracing? Does the same thing
> happen when you are not tracing and simply running the script as normal?
>
> Paul Shoemaker | Application Developer
> paul.shoemaker[@]helloecho.com
> 615.290.4342 ph | 615.777.5119 fax
>
> echo | Hello. Hello. | helloecho.com
>
>
>
> ________________________________
> From: istemi ekin akkuş <ekin.akkus[@]gmail.com>
> Date: Tue, 17 Mar 2009 13:33:39 -0500
> To: <xdebug-general[@]lists.xdebug.org>
> Subject: [xdebug-general] xdebug 2.0.4 memory leak?
>
> Hello,
>
> I am using a pristine Ubuntu 8.0.4 with Apache/2.2.8 pre-fork module
> with PHP 5.2.4-ubuntu5.5 with xdebug 2.0.4.
>
> I have realized that after a function is called many times, it seems
> that memory gets exhausted. I tried it without xdebug installed and
> did not encounter any memory problems.
>
> I have checked the mailing list whether this issue was reported
> before, only saw a report about profiler memory leak in version 1.3.2
> (which was resolved not to be fixed, stating that xdebug2 does not
> have any of these issues).
>
> Here is a simple code that creates the issue:
>
> <?php
> $a = 'foo';
> function bar($a)
> {
> $b = $a;
> }
> for ($i = 0; $i < 250000; $i++) {
> bar($a);
> }
> ?>
>
> I am not using nor profiler, neither debugger. Just tracing
> functionality. I don't think I am using a weird option that is set so
> that it will create a memory leak, but I believe the more eyes looking
> at a configuration, the better. Here are the relevant xdebug.ini
> options:
>
> ; General
> xdebug.auto_trace=on
> xdebug.collect_includes=0
> xdebug.collect_params=4
> xdebug.collect_return=on
> xdebug.default_enable=on
> xdebug.extended_info=1
> xdebug.manual_url=http://www.php.net
> xdebug.show_local_vars=on
> xdebug.show_mem_delta=1
> xdebug.max_nesting_level=100
>
> xdebug.dump_globals=on
> xdebug.dump.GET=*
> xdebug.dump.POST=*
> xdebug.dump.SERVER=*
> xdebug.dump.COOKIE=*
> xdebug.dump.REQUEST=*
> xdebug.dump.SESSION=*
> xdebug.dump.FILES=*
> xdebug.dump_undefined=off
> xdebug.var_display_max_depth=50
> xdebug.var_display_max_children=500
> xdebug.collect_vars=on
>
> Thank you.
> Best,
>
> ekin
>
>
> CONFIDENTIALITY NOTICE:
>
> This e-mail transmission, and any documents or files attached to it, may
> contain confidential information.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or
> use of any of the information contained in or attached to this message is
> STRICTLY PROHIBITED. If you
> have received this transmission in error, please immediately notify the
> sender by reply email, and
> destroy the original transmission and its attachments without reading or
> saving them. Thank you.
>
Received on Tue Mar 17 2009 - 22:04:43 GMT