[xdebug-dev] Bug 0000335: xdebug uses enormous amounts of memory when tracing or profiling long running scripts.

The following NEW bug has been ADDED.
======================================================================
http://bugs.xdebug.org/bug_view_page.php?bug_id=0000335
======================================================================
Reporter: lars
Handler:
======================================================================
Project: Xdebug
Bug ID: 335
Category: Usage problems
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Operating System: Debian Etch
PHP Version: 5.2.0
Xdebug Version: 2.1.0-dev
======================================================================
Date Submitted: 2007-11-14 06:42 CET
Last Modified: 2007-11-14 06:42 CET
======================================================================
Summary: xdebug uses enormous amounts of memory when tracing or profiling long running scripts.
Description:
While debugging an export script which exports some hundred megabytes of
data to a csv file I noticed that the apache consumed increasing amounts
of memory.

,----[ ps uax ]---
| USER PID %CPU %MEM VSZ RSS TTY STAT START TIME
COMMAND
| www-data 9488 4.6 68.5 1052576 709888 ? S 05:12 3:05
/usr/sbin/apache2 -k start
`----

I discoverd with lsof that this apache process was the one which had php
running to export the data. PHP has a configured memory limit of 64MB and
also they're no data structures in the script which could hold such
enormous amount of data.

Is this a known problem?
======================================================================

Bug History
Date Modified Username Field Change
======================================================================
2007-11-14 06:42lars New Bug
2007-11-14 06:42lars Bug Monitored: lars
======================================================================
Received on Wed Nov 14 2007 - 06:42:26 GMT