[xdebug-general] Re: PHP5 DOM memory coverage

From: Derick Rethans <derick[@]xdebug.org>
Date: Fri, 1 Jul 2005 16:49:20 +0200 (CEST)

On Thu, 30 Jun 2005, Michael Kimsal wrote:

> I'm seeing memory usage numbers in xdebug which don't make sense.  We're using
> the PHP5 DOM extension  to load a file.  The files themselves are easily over
> 200k, yet after doing a domdocument->load, I see no significant change
>     0.1480    4723008     +536             ->
> DOMDocument->load() /data/web/root/cms/tisco/live/ses_core-4.5.101/application/cms4_module_salescatalog/classes/ActionProcessor.clss:824
>     0.1489    4722896 +4294967184             ->
> XSLTProcessor->importStylesheet() /data/web/root/cms/tisco/live/ses_core-4.5.101/application/cms4_module_salescatalog/classes/ActionProcessor.clss:824
> Additionally, as you can see, when the memory usage goes down, the delta is
> +4gig.  But that's not why I'm writing.  :)

Hmm, that seems to be a signed and/or 64bit issue btw - I should fix
that too.

> That DOMDocument->load() was loading a file that was probably 220k, yet xdebug
> is only reporting a change of 536 bytes in memory usage.
> Is there something else I need to setup to track DOM memory usage?  Is this a
> known (or unknown?!) issue with xdebug?

It has little to do with Xdebug - PHP's DOM Extension doesn't use Zend's
memory manager, and thus there is no information available in the engine
that Xdebug can use to show you the internal memory usage.


Xdebug | http://xdebug.org | xdebug-general@lists.xdebug.org
Received on Fri Jul 01 2005 - 16:49:24 BST

This archive was generated by hypermail 2.2.0 : Mon Jun 25 2018 - 06:00:04 BST