Edit report at https://pear.php.net/bugs/bug.php?id=7563&edit=1

ID: 7563
Updated by: demon.gene@gmail.com
Reported By: jan at horde dot org
Summary: Improve memory usage
Status: Open
Type: Feature/Change Request
Package: PhpDocumentor
Operating System: FreeBSD 4.11-STABLE
Package Version: 1.3.0RC6
PHP Version: 4.3.11
Roadmap Versions:
New Comment:

An option to consider --

Previous Comments:

[2011-01-15 14:40:30] reinierk

What I am missing from this discussion is WHY? WHY is memory usage so
outrageous. I am compiling documentation for openbiz some 168764 lines
of code in 695 files This consumes 580M of memory. That comes to ~1M per
file and 3.6Kb per line of code!
Surely this can be done much more efficient with less memory.
Maybe its worth investigating where memory is used, where memory can be
released etc...


[2010-06-09 15:24:41] wcomnisky

I have the same problem (allowed memory size exhausted) while trying to
generate the documentation of my models, generated by Propel (113 model
classes, with their peers, map builders and base classes - 565 files).

Ubuntu 9.10
PHP 5.2.10-2ubuntu6.4 with Suhosin-Patch 0.9.7 (cli)
Zend Engine v2.2.0 with Xdebug v2.0.4

phpDocumentor version 1.4.3
Maximum memory usage set at 512M by phpDocumentor.ini
using tokenizer Parser

[exec] Fatal error: Allowed memory size of 536870912 bytes exhausted
(tried to allocate 35 bytes) in
on line 303
[exec] Call Stack:
[exec] 0.0006 57828 1. {main}() /usr/bin/phpdoc:0
[exec] 0.0011 66360 2.
[exec] 0.1359 9419524 3. phpDocumentor_setup->createDocs()
[exec] 107.1463 533144076 4. phpDocumentorTParser->parse()
[exec] 107.1516 530961380 5.
[exec] 107.1517 530961444 6. phpDocumentorTWordParser->setup()
[exec] 107.1639 534709464 7.
[exec] 107.2731 536752240 8. phpDocumentorTWordParser->addSource()
[exec] 107.2731 536752832 9. str_replace()
[exec] Result: 255

(running with Ant)


[2010-04-08 18:35:20] protatoe

Sorry to add to an old thread, but I was quiet surprised to see this
still an issue 4 years after it was reported.

Even at a 1GB of ram, it's still failing to parse out the documentation.
This only started happening after recompiling with tokenizer support,
because it was failing for different reasons with out.


[2007-01-10 15:59:48] ashnazg at php dot net

SF patch #1588942 is now committed to CVS, so memory_limit will now be
configurable in the INI file.


[2006-12-18 15:29:04] cellog

the patch simply allows setting memory_limit, which does
not in fact improve memory usage, so no, this is a
separate and massive undertaking that is planned for 2.0


The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at

Search Discussions

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
grouppear-bugs @
postedJan 23, '12 at 6:09p
activeJan 23, '12 at 6:09p

1 user in discussion

Demon Gene: 1 post



site design / logo © 2022 Grokbase