#22774 [Com]: PHP crashes when exiting (long XML doc)
| From: | ion3l at yahoo dot com | Date: | Wed, 30 Jun 2004 10:03:55 +0000 |
| Subject: | #22774 [Com]: PHP crashes when exiting (long XML doc) | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-61548@lists.php.net to get a copy of this message | ||
ID: 22774
Comment by: ion3l at yahoo dot com
Reported By: fgarcia at uef dot es
Status: Closed
Bug Type: DOM XML related
Operating System: Windows 2000
PHP Version: 4.3.2RC1
New Comment:
i WAMT DRIVERS FOR THE SOUND CARD AND THE VIDEO CARD PLEASE
Previous Comments:
------------------------------------------------------------------------
[2003-04-07 02:17:45] fgarcia at uef dot es
I've tried
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
and works fine.
Thanks.
Fernando
------------------------------------------------------------------------
[2003-04-03 04:38:00] chregu@php.net
Please try using this CVS snapshot:
http://snaps.php.net/php4-STABLE-latest.tar.gz
For Windows:
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
Should be fixed in the stable release, as well.
------------------------------------------------------------------------
[2003-03-27 11:24:14] rrichards at digarc dot com
Finally able to reproduce this using a simplified script:
<?php
if (!extension_loaded("domxml")) @dl("php_domxml.dll");
$domR=domxml_new_doc('1.0');
$nItinerario = $domR->create_element("itinerario");
$domR->append_child($nItinerario);
?>
If the extension is NOT loaded via the php.ini file, upon shutdown,
php_free_xml_doc is called first and then php_free_xml_node for the
created element is called which causes the blow up. If read from the
ini file, php_free_xml_node is called first and then php_free_xml_doc.
Seems to be some issue with the external loading of the extension.
------------------------------------------------------------------------
[2003-03-24 05:02:02] rrichards at digarc dot com
Am not able to reproduce in Win 2K. Ran it for 10,000 and 20,000
iterations without a problem. Finally ran it for 1,000,000 iterations
until the machine ran out of memory (was over a Gig of used memory at
that point).
Once getting a fatal emalloc error memory returned back to normal
(exact amount used prior to running).
Tested against latest cvs code as well as a php4-3.0-dev build from jun
2002.
using libxml2-2.4.22
------------------------------------------------------------------------
[2003-03-21 05:43:43] chregu@php.net
looks like a mem-leak
linux normally doesn't segfault on memleaks. Windows does... that's the
difference ;)
I try to look at it
------------------------------------------------------------------------
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
http://bugs.php.net/22774
--
Edit this bug report at http://bugs.php.net/?id=22774&edit=1