Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Closed
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
GREAT !
I was sufferring (the same ) bug using the latest PHP binaries with:
$dom = domxml_open_file("tests/huge.xml");
$array = $dom->get_elements_by_tagname('document');
foreach($array as $e) {
echo "" . $e->get_attribute("id");
}
using 'php4-win32-STABLE-latest.zip' its works !!
many thanks
Previous Comments:
[2002-05-18 08:37:10] [EMAIL PROTECTED]
There is a stable snapshot available with (hopefully) the
memleak-fixes. You can get it at
http://snaps.php.net/win32/php4-win32-STABLE-latest.zip
Please report, if it works on Windows now.
[2002-05-17 13:10:50] [EMAIL PROTECTED]
My patch is available at
http://trash.chregu.tv/domxml-memleak.diff
(for CVS-HEAD, but should be applyable to PHP_4_2_0 branch as well)
The big memory hole is certainly fixed with that, don't know about
windows and the little memleaks...
Would be great, if someone could test it.
[2002-05-17 11:44:09] [EMAIL PROTECTED]
Other people sit at the lake and enjoy the stupid hot weather here, i
hunt memory leaks... what a pleasure... But i found it. Nodes which had
no parents were not freed. i have a fix, but it's not perfect yet.
expect a patch soon.
[2002-05-17 07:44:01] [EMAIL PROTECTED]
Ok, i did some tests on linux and indeed
There is a big f**king memory hole in domxml with
append_child/append_sibling :( even with Josephs patch.
I will investigate further today...
[2002-05-16 19:17:32] [EMAIL PROTECTED]
Oh, and I've tested it to work with 70,000 elements...
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/16888
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Analyzed +Status: Closed Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: There is a stable snapshot available with (hopefully) the memleak-fixes. You can get it at http://snaps.php.net/win32/php4-win32-STABLE-latest.zip Please report, if it works on Windows now. Previous Comments: [2002-05-17 13:10:50] [EMAIL PROTECTED] My patch is available at http://trash.chregu.tv/domxml-memleak.diff (for CVS-HEAD, but should be applyable to PHP_4_2_0 branch as well) The big memory hole is certainly fixed with that, don't know about windows and the little memleaks... Would be great, if someone could test it. [2002-05-17 11:44:09] [EMAIL PROTECTED] Other people sit at the lake and enjoy the stupid hot weather here, i hunt memory leaks... what a pleasure... But i found it. Nodes which had no parents were not freed. i have a fix, but it's not perfect yet. expect a patch soon. [2002-05-17 07:44:01] [EMAIL PROTECTED] Ok, i did some tests on linux and indeed There is a big f**king memory hole in domxml with append_child/append_sibling :( even with Josephs patch. I will investigate further today... [2002-05-16 19:17:32] [EMAIL PROTECTED] Oh, and I've tested it to work with 70,000 elements... [2002-05-16 19:04:25] [EMAIL PROTECTED] I seem to have found the problem. Nodes are being freed twice: once in a call to php_free_xml_node, and once in a call to node_wrapper_dtor. I've made two changes, one i've replaced the "free" code in php_free_xml_node with a call to the static inline function node_wrapper_dtor, and then call dom_object_set_data to clear the data (a check should be put here to make sure that the refcount is 0 before doing this, but I don't have time right now). I'll post the patch to the php-dev list so that people can look it over, and make sure that it doesn't introduce any memory leaks. I'll mark the bug fixed when I commit my change. 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Analyzed Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: My patch is available at http://trash.chregu.tv/domxml-memleak.diff (for CVS-HEAD, but should be applyable to PHP_4_2_0 branch as well) The big memory hole is certainly fixed with that, don't know about windows and the little memleaks... Would be great, if someone could test it. Previous Comments: [2002-05-17 11:44:09] [EMAIL PROTECTED] Other people sit at the lake and enjoy the stupid hot weather here, i hunt memory leaks... what a pleasure... But i found it. Nodes which had no parents were not freed. i have a fix, but it's not perfect yet. expect a patch soon. [2002-05-17 07:44:01] [EMAIL PROTECTED] Ok, i did some tests on linux and indeed There is a big f**king memory hole in domxml with append_child/append_sibling :( even with Josephs patch. I will investigate further today... [2002-05-16 19:17:32] [EMAIL PROTECTED] Oh, and I've tested it to work with 70,000 elements... [2002-05-16 19:04:25] [EMAIL PROTECTED] I seem to have found the problem. Nodes are being freed twice: once in a call to php_free_xml_node, and once in a call to node_wrapper_dtor. I've made two changes, one i've replaced the "free" code in php_free_xml_node with a call to the static inline function node_wrapper_dtor, and then call dom_object_set_data to clear the data (a check should be put here to make sure that the refcount is 0 before doing this, but I don't have time right now). I'll post the patch to the php-dev list so that people can look it over, and make sure that it doesn't introduce any memory leaks. I'll mark the bug fixed when I commit my change. [2002-05-16 15:59:08] [EMAIL PROTECTED] Ahh, Now I'm understanding the original poster. I never got the 404 page. Must have been a browser specific issue. The error occurs in the cleanup routines on both iis and apache. The stack trace is as follows: _zval_ptr_dtor(_zval_struct * * 0x00e2f568, char * 0x10023020 `string', unsigned int 0x01f8) line 272 + 5 bytes node_wrapper_dtor(_xmlNode * 0x005cb9c8) line 504 + 26 bytes node_list_wrapper_dtor(_xmlNode * 0x005cb9c8) line 531 + 9 bytes node_list_wrapper_dtor(_xmlNode * 0x005c3c18) line 521 + 12 bytes php_free_xml_doc(_zend_rsrc_list_entry * 0x00e38e18, void * * * 0x00afe7a8) line 563 + 12 bytes list_entry_destructor(void * 0x00e38e18) line 177 + 16 bytes zend_hash_apply_deleter(_hashtable * 0x00b2cac4, bucket * 0x00e38db8) line 596 + 15 bytes zend_hash_graceful_reverse_destroy(_hashtable * 0x00b2cac4) line 662 + 13 bytes zend_destroy_rsrc_list(_hashtable * 0x00b2cac4, void * * * 0x00afe7a8) line 233 + 9 bytes shutdown_executor(void * * * 0x00afe7a8) line 196 + 30 bytes zend_deactivate(void * * * 0x00afe7a8) line 596 + 9 bytes php_request_shutdown(void * 0x) line 787 + 9 bytes apache_php_module_main(request_rec * 0x00afc798, int 0x, void * * * 0x00afe7a8) line 96 + 8 bytes send_php(request_rec * 0x00afc798, int 0x, char * 0x00afd248) line 575 + 17 bytes send_parsed_php(request_rec * 0x00afc798) line 590 + 13 bytes ap_invoke_handler(request_rec * 0x00afc798) line 517 + 10 bytes process_request_internal(request_rec * 0x00afc798) line 1308 + 9 bytes ap_process_request(request_rec * 0x00afc798) line 1324 + 9 bytes child_sub_main(int 0x) line 5881 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Critical +Status: Analyzed Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: Other people sit at the lake and enjoy the stupid hot weather here, i hunt memory leaks... what a pleasure... But i found it. Nodes which had no parents were not freed. i have a fix, but it's not perfect yet. expect a patch soon. Previous Comments: [2002-05-17 07:44:01] [EMAIL PROTECTED] Ok, i did some tests on linux and indeed There is a big f**king memory hole in domxml with append_child/append_sibling :( even with Josephs patch. I will investigate further today... [2002-05-16 19:17:32] [EMAIL PROTECTED] Oh, and I've tested it to work with 70,000 elements... [2002-05-16 19:04:25] [EMAIL PROTECTED] I seem to have found the problem. Nodes are being freed twice: once in a call to php_free_xml_node, and once in a call to node_wrapper_dtor. I've made two changes, one i've replaced the "free" code in php_free_xml_node with a call to the static inline function node_wrapper_dtor, and then call dom_object_set_data to clear the data (a check should be put here to make sure that the refcount is 0 before doing this, but I don't have time right now). I'll post the patch to the php-dev list so that people can look it over, and make sure that it doesn't introduce any memory leaks. I'll mark the bug fixed when I commit my change. [2002-05-16 15:59:08] [EMAIL PROTECTED] Ahh, Now I'm understanding the original poster. I never got the 404 page. Must have been a browser specific issue. The error occurs in the cleanup routines on both iis and apache. The stack trace is as follows: _zval_ptr_dtor(_zval_struct * * 0x00e2f568, char * 0x10023020 `string', unsigned int 0x01f8) line 272 + 5 bytes node_wrapper_dtor(_xmlNode * 0x005cb9c8) line 504 + 26 bytes node_list_wrapper_dtor(_xmlNode * 0x005cb9c8) line 531 + 9 bytes node_list_wrapper_dtor(_xmlNode * 0x005c3c18) line 521 + 12 bytes php_free_xml_doc(_zend_rsrc_list_entry * 0x00e38e18, void * * * 0x00afe7a8) line 563 + 12 bytes list_entry_destructor(void * 0x00e38e18) line 177 + 16 bytes zend_hash_apply_deleter(_hashtable * 0x00b2cac4, bucket * 0x00e38db8) line 596 + 15 bytes zend_hash_graceful_reverse_destroy(_hashtable * 0x00b2cac4) line 662 + 13 bytes zend_destroy_rsrc_list(_hashtable * 0x00b2cac4, void * * * 0x00afe7a8) line 233 + 9 bytes shutdown_executor(void * * * 0x00afe7a8) line 196 + 30 bytes zend_deactivate(void * * * 0x00afe7a8) line 596 + 9 bytes php_request_shutdown(void * 0x) line 787 + 9 bytes apache_php_module_main(request_rec * 0x00afc798, int 0x, void * * * 0x00afe7a8) line 96 + 8 bytes send_php(request_rec * 0x00afc798, int 0x, char * 0x00afd248) line 575 + 17 bytes send_parsed_php(request_rec * 0x00afc798) line 590 + 13 bytes ap_invoke_handler(request_rec * 0x00afc798) line 517 + 10 bytes process_request_internal(request_rec * 0x00afc798) line 1308 + 9 bytes ap_process_request(request_rec * 0x00afc798) line 1324 + 9 bytes child_sub_main(int 0x) line 5881 [2002-05-16 14:05:41] [EMAIL PROTECTED] The crash occurs weather you use append_sibling or append_child 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] -Status: Open +Status: Critical Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: Ok, i did some tests on linux and indeed There is a big f**king memory hole in domxml with append_child/append_sibling :( even with Josephs patch. I will investigate further today... Previous Comments: [2002-05-16 19:17:32] [EMAIL PROTECTED] Oh, and I've tested it to work with 70,000 elements... [2002-05-16 19:04:25] [EMAIL PROTECTED] I seem to have found the problem. Nodes are being freed twice: once in a call to php_free_xml_node, and once in a call to node_wrapper_dtor. I've made two changes, one i've replaced the "free" code in php_free_xml_node with a call to the static inline function node_wrapper_dtor, and then call dom_object_set_data to clear the data (a check should be put here to make sure that the refcount is 0 before doing this, but I don't have time right now). I'll post the patch to the php-dev list so that people can look it over, and make sure that it doesn't introduce any memory leaks. I'll mark the bug fixed when I commit my change. [2002-05-16 15:59:08] [EMAIL PROTECTED] Ahh, Now I'm understanding the original poster. I never got the 404 page. Must have been a browser specific issue. The error occurs in the cleanup routines on both iis and apache. The stack trace is as follows: _zval_ptr_dtor(_zval_struct * * 0x00e2f568, char * 0x10023020 `string', unsigned int 0x01f8) line 272 + 5 bytes node_wrapper_dtor(_xmlNode * 0x005cb9c8) line 504 + 26 bytes node_list_wrapper_dtor(_xmlNode * 0x005cb9c8) line 531 + 9 bytes node_list_wrapper_dtor(_xmlNode * 0x005c3c18) line 521 + 12 bytes php_free_xml_doc(_zend_rsrc_list_entry * 0x00e38e18, void * * * 0x00afe7a8) line 563 + 12 bytes list_entry_destructor(void * 0x00e38e18) line 177 + 16 bytes zend_hash_apply_deleter(_hashtable * 0x00b2cac4, bucket * 0x00e38db8) line 596 + 15 bytes zend_hash_graceful_reverse_destroy(_hashtable * 0x00b2cac4) line 662 + 13 bytes zend_destroy_rsrc_list(_hashtable * 0x00b2cac4, void * * * 0x00afe7a8) line 233 + 9 bytes shutdown_executor(void * * * 0x00afe7a8) line 196 + 30 bytes zend_deactivate(void * * * 0x00afe7a8) line 596 + 9 bytes php_request_shutdown(void * 0x) line 787 + 9 bytes apache_php_module_main(request_rec * 0x00afc798, int 0x, void * * * 0x00afe7a8) line 96 + 8 bytes send_php(request_rec * 0x00afc798, int 0x, char * 0x00afd248) line 575 + 17 bytes send_parsed_php(request_rec * 0x00afc798) line 590 + 13 bytes ap_invoke_handler(request_rec * 0x00afc798) line 517 + 10 bytes process_request_internal(request_rec * 0x00afc798) line 1308 + 9 bytes ap_process_request(request_rec * 0x00afc798) line 1324 + 9 bytes child_sub_main(int 0x) line 5881 [2002-05-16 14:05:41] [EMAIL PROTECTED] The crash occurs weather you use append_sibling or append_child [2002-05-16 13:29:39] [EMAIL PROTECTED] To narrow down the problem. Does it also crash, when you don't use append_sibling, but append_child in the for-loop? chregu 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
Oh, and I've tested it to work with 70,000 elements...
Previous Comments:
[2002-05-16 19:04:25] [EMAIL PROTECTED]
I seem to have found the problem. Nodes are being freed twice: once in
a call to php_free_xml_node, and once in a call to node_wrapper_dtor.
I've made two changes, one i've replaced the "free" code in
php_free_xml_node with a call to the static inline function
node_wrapper_dtor, and then call dom_object_set_data to clear the data
(a check should be put here to make sure that the refcount is 0 before
doing this, but I don't have time right now). I'll post the patch to
the php-dev list so that people can look it over, and make sure that it
doesn't introduce any memory leaks. I'll mark the bug fixed when I
commit my change.
[2002-05-16 15:59:08] [EMAIL PROTECTED]
Ahh, Now I'm understanding the original poster. I never got the 404
page. Must have been a browser specific issue. The error occurs in
the cleanup routines on both iis and apache. The stack trace is as
follows:
_zval_ptr_dtor(_zval_struct * * 0x00e2f568, char * 0x10023020 `string',
unsigned int 0x01f8) line 272 + 5 bytes
node_wrapper_dtor(_xmlNode * 0x005cb9c8) line 504 + 26 bytes
node_list_wrapper_dtor(_xmlNode * 0x005cb9c8) line 531 + 9 bytes
node_list_wrapper_dtor(_xmlNode * 0x005c3c18) line 521 + 12 bytes
php_free_xml_doc(_zend_rsrc_list_entry * 0x00e38e18, void * * *
0x00afe7a8) line 563 + 12 bytes
list_entry_destructor(void * 0x00e38e18) line 177 + 16 bytes
zend_hash_apply_deleter(_hashtable * 0x00b2cac4, bucket * 0x00e38db8)
line 596 + 15 bytes
zend_hash_graceful_reverse_destroy(_hashtable * 0x00b2cac4) line 662 +
13 bytes
zend_destroy_rsrc_list(_hashtable * 0x00b2cac4, void * * * 0x00afe7a8)
line 233 + 9 bytes
shutdown_executor(void * * * 0x00afe7a8) line 196 + 30 bytes
zend_deactivate(void * * * 0x00afe7a8) line 596 + 9 bytes
php_request_shutdown(void * 0x) line 787 + 9 bytes
apache_php_module_main(request_rec * 0x00afc798, int 0x, void *
* * 0x00afe7a8) line 96 + 8 bytes
send_php(request_rec * 0x00afc798, int 0x, char * 0x00afd248)
line 575 + 17 bytes
send_parsed_php(request_rec * 0x00afc798) line 590 + 13 bytes
ap_invoke_handler(request_rec * 0x00afc798) line 517 + 10 bytes
process_request_internal(request_rec * 0x00afc798) line 1308 + 9 bytes
ap_process_request(request_rec * 0x00afc798) line 1324 + 9 bytes
child_sub_main(int 0x) line 5881
[2002-05-16 14:05:41] [EMAIL PROTECTED]
The crash occurs weather you use append_sibling or append_child
[2002-05-16 13:29:39] [EMAIL PROTECTED]
To narrow down the problem. Does it also crash, when you don't use
append_sibling, but append_child in the for-loop?
chregu
[2002-05-16 13:03:37] [EMAIL PROTECTED]
even with the new php_domxml.dll it still crashes
also when you use the correct new function
append_sibling() it still crashes, even worser when you forget to add
content to your nodes as in the example above apache crashes in a loop
until the timeout is reached and no output reaches the browser.
create_element("HTML");
$root = $doc->append_child($root);
$body = $doc->create_element("element");
$body = $root->append_child($body);
//$body->set_content("content");
for($i = 1; $i < 130; $i++){
$element = $doc->create_element("element");
//$element->set_content("content ".$i);
$body->append_sibling($element);
}
echo htmlentities($doc->dump_mem(true));
?>
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/16888
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
I seem to have found the problem. Nodes are being freed twice: once in
a call to php_free_xml_node, and once in a call to node_wrapper_dtor.
I've made two changes, one i've replaced the "free" code in
php_free_xml_node with a call to the static inline function
node_wrapper_dtor, and then call dom_object_set_data to clear the data
(a check should be put here to make sure that the refcount is 0 before
doing this, but I don't have time right now). I'll post the patch to
the php-dev list so that people can look it over, and make sure that it
doesn't introduce any memory leaks. I'll mark the bug fixed when I
commit my change.
Previous Comments:
[2002-05-16 15:59:08] [EMAIL PROTECTED]
Ahh, Now I'm understanding the original poster. I never got the 404
page. Must have been a browser specific issue. The error occurs in
the cleanup routines on both iis and apache. The stack trace is as
follows:
_zval_ptr_dtor(_zval_struct * * 0x00e2f568, char * 0x10023020 `string',
unsigned int 0x01f8) line 272 + 5 bytes
node_wrapper_dtor(_xmlNode * 0x005cb9c8) line 504 + 26 bytes
node_list_wrapper_dtor(_xmlNode * 0x005cb9c8) line 531 + 9 bytes
node_list_wrapper_dtor(_xmlNode * 0x005c3c18) line 521 + 12 bytes
php_free_xml_doc(_zend_rsrc_list_entry * 0x00e38e18, void * * *
0x00afe7a8) line 563 + 12 bytes
list_entry_destructor(void * 0x00e38e18) line 177 + 16 bytes
zend_hash_apply_deleter(_hashtable * 0x00b2cac4, bucket * 0x00e38db8)
line 596 + 15 bytes
zend_hash_graceful_reverse_destroy(_hashtable * 0x00b2cac4) line 662 +
13 bytes
zend_destroy_rsrc_list(_hashtable * 0x00b2cac4, void * * * 0x00afe7a8)
line 233 + 9 bytes
shutdown_executor(void * * * 0x00afe7a8) line 196 + 30 bytes
zend_deactivate(void * * * 0x00afe7a8) line 596 + 9 bytes
php_request_shutdown(void * 0x) line 787 + 9 bytes
apache_php_module_main(request_rec * 0x00afc798, int 0x, void *
* * 0x00afe7a8) line 96 + 8 bytes
send_php(request_rec * 0x00afc798, int 0x, char * 0x00afd248)
line 575 + 17 bytes
send_parsed_php(request_rec * 0x00afc798) line 590 + 13 bytes
ap_invoke_handler(request_rec * 0x00afc798) line 517 + 10 bytes
process_request_internal(request_rec * 0x00afc798) line 1308 + 9 bytes
ap_process_request(request_rec * 0x00afc798) line 1324 + 9 bytes
child_sub_main(int 0x) line 5881
[2002-05-16 14:05:41] [EMAIL PROTECTED]
The crash occurs weather you use append_sibling or append_child
[2002-05-16 13:29:39] [EMAIL PROTECTED]
To narrow down the problem. Does it also crash, when you don't use
append_sibling, but append_child in the for-loop?
chregu
[2002-05-16 13:03:37] [EMAIL PROTECTED]
even with the new php_domxml.dll it still crashes
also when you use the correct new function
append_sibling() it still crashes, even worser when you forget to add
content to your nodes as in the example above apache crashes in a loop
until the timeout is reached and no output reaches the browser.
create_element("HTML");
$root = $doc->append_child($root);
$body = $doc->create_element("element");
$body = $root->append_child($body);
//$body->set_content("content");
for($i = 1; $i < 130; $i++){
$element = $doc->create_element("element");
//$element->set_content("content ".$i);
$body->append_sibling($element);
}
echo htmlentities($doc->dump_mem(true));
?>
[2002-05-16 11:06:57] [EMAIL PROTECTED]
I'm looking into it. No guarantees though. I tried it with IIS, and
it seemed to work ok (Well the domxml part), it just crashed later.
I'm installing Apache to see if I can reproduce the problem/fix 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/16888
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
Ahh, Now I'm understanding the original poster. I never got the 404
page. Must have been a browser specific issue. The error occurs in
the cleanup routines on both iis and apache. The stack trace is as
follows:
_zval_ptr_dtor(_zval_struct * * 0x00e2f568, char * 0x10023020 `string',
unsigned int 0x01f8) line 272 + 5 bytes
node_wrapper_dtor(_xmlNode * 0x005cb9c8) line 504 + 26 bytes
node_list_wrapper_dtor(_xmlNode * 0x005cb9c8) line 531 + 9 bytes
node_list_wrapper_dtor(_xmlNode * 0x005c3c18) line 521 + 12 bytes
php_free_xml_doc(_zend_rsrc_list_entry * 0x00e38e18, void * * *
0x00afe7a8) line 563 + 12 bytes
list_entry_destructor(void * 0x00e38e18) line 177 + 16 bytes
zend_hash_apply_deleter(_hashtable * 0x00b2cac4, bucket * 0x00e38db8)
line 596 + 15 bytes
zend_hash_graceful_reverse_destroy(_hashtable * 0x00b2cac4) line 662 +
13 bytes
zend_destroy_rsrc_list(_hashtable * 0x00b2cac4, void * * * 0x00afe7a8)
line 233 + 9 bytes
shutdown_executor(void * * * 0x00afe7a8) line 196 + 30 bytes
zend_deactivate(void * * * 0x00afe7a8) line 596 + 9 bytes
php_request_shutdown(void * 0x) line 787 + 9 bytes
apache_php_module_main(request_rec * 0x00afc798, int 0x, void *
* * 0x00afe7a8) line 96 + 8 bytes
send_php(request_rec * 0x00afc798, int 0x, char * 0x00afd248)
line 575 + 17 bytes
send_parsed_php(request_rec * 0x00afc798) line 590 + 13 bytes
ap_invoke_handler(request_rec * 0x00afc798) line 517 + 10 bytes
process_request_internal(request_rec * 0x00afc798) line 1308 + 9 bytes
ap_process_request(request_rec * 0x00afc798) line 1324 + 9 bytes
child_sub_main(int 0x) line 5881
Previous Comments:
[2002-05-16 14:05:41] [EMAIL PROTECTED]
The crash occurs weather you use append_sibling or append_child
[2002-05-16 13:29:39] [EMAIL PROTECTED]
To narrow down the problem. Does it also crash, when you don't use
append_sibling, but append_child in the for-loop?
chregu
[2002-05-16 13:03:37] [EMAIL PROTECTED]
even with the new php_domxml.dll it still crashes
also when you use the correct new function
append_sibling() it still crashes, even worser when you forget to add
content to your nodes as in the example above apache crashes in a loop
until the timeout is reached and no output reaches the browser.
create_element("HTML");
$root = $doc->append_child($root);
$body = $doc->create_element("element");
$body = $root->append_child($body);
//$body->set_content("content");
for($i = 1; $i < 130; $i++){
$element = $doc->create_element("element");
//$element->set_content("content ".$i);
$body->append_sibling($element);
}
echo htmlentities($doc->dump_mem(true));
?>
[2002-05-16 11:06:57] [EMAIL PROTECTED]
I'm looking into it. No guarantees though. I tried it with IIS, and
it seemed to work ok (Well the domxml part), it just crashed later.
I'm installing Apache to see if I can reproduce the problem/fix it.
[2002-05-16 09:07:01] [EMAIL PROTECTED]
Edin created a new php_domxml.dll with libxml2-2.4.21 compile d in.
It's available at
http://ftp.proventum.net/pub/php/win32/php_domxml.zip
Can you check that. But i fear, it doesn't help solve the problem :(
Please be aware, that append_child changed the meaning in 4.2.1. The
former append_child is now append_sibling, and append_child behaves
like the w3c likes it. But appending a sibling to the root node,
doesn't make really sense, but it souldn't crash PHP, either :)
I would be very glad, if someone with windows programming experience
could hunt down the problem.
chregu
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/16888
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
The crash occurs weather you use append_sibling or append_child
Previous Comments:
[2002-05-16 13:29:39] [EMAIL PROTECTED]
To narrow down the problem. Does it also crash, when you don't use
append_sibling, but append_child in the for-loop?
chregu
[2002-05-16 13:03:37] [EMAIL PROTECTED]
even with the new php_domxml.dll it still crashes
also when you use the correct new function
append_sibling() it still crashes, even worser when you forget to add
content to your nodes as in the example above apache crashes in a loop
until the timeout is reached and no output reaches the browser.
create_element("HTML");
$root = $doc->append_child($root);
$body = $doc->create_element("element");
$body = $root->append_child($body);
//$body->set_content("content");
for($i = 1; $i < 130; $i++){
$element = $doc->create_element("element");
//$element->set_content("content ".$i);
$body->append_sibling($element);
}
echo htmlentities($doc->dump_mem(true));
?>
[2002-05-16 11:06:57] [EMAIL PROTECTED]
I'm looking into it. No guarantees though. I tried it with IIS, and
it seemed to work ok (Well the domxml part), it just crashed later.
I'm installing Apache to see if I can reproduce the problem/fix it.
[2002-05-16 09:07:01] [EMAIL PROTECTED]
Edin created a new php_domxml.dll with libxml2-2.4.21 compile d in.
It's available at
http://ftp.proventum.net/pub/php/win32/php_domxml.zip
Can you check that. But i fear, it doesn't help solve the problem :(
Please be aware, that append_child changed the meaning in 4.2.1. The
former append_child is now append_sibling, and append_child behaves
like the w3c likes it. But appending a sibling to the root node,
doesn't make really sense, but it souldn't crash PHP, either :)
I would be very glad, if someone with windows programming experience
could hunt down the problem.
chregu
[2002-05-15 17:50:13] [EMAIL PROTECTED]
FWIW, the sample script works ok using the latest HEAD under IIS in
debug mode...well, works is an approximation. It doesn't crash until
the Zend tries to clean up memory, and then crashes in _zval_ptr_dtor.
Not feeling like a Zend guru today, I don't feel like attacking it.
I'll try Apache though to see if I can narrow this bug down.
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/16888
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Feedback
+Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
To narrow down the problem. Does it also crash, when you don't use
append_sibling, but append_child in the for-loop?
chregu
Previous Comments:
[2002-05-16 13:03:37] [EMAIL PROTECTED]
even with the new php_domxml.dll it still crashes
also when you use the correct new function
append_sibling() it still crashes, even worser when you forget to add
content to your nodes as in the example above apache crashes in a loop
until the timeout is reached and no output reaches the browser.
create_element("HTML");
$root = $doc->append_child($root);
$body = $doc->create_element("element");
$body = $root->append_child($body);
//$body->set_content("content");
for($i = 1; $i < 130; $i++){
$element = $doc->create_element("element");
//$element->set_content("content ".$i);
$body->append_sibling($element);
}
echo htmlentities($doc->dump_mem(true));
?>
[2002-05-16 11:06:57] [EMAIL PROTECTED]
I'm looking into it. No guarantees though. I tried it with IIS, and
it seemed to work ok (Well the domxml part), it just crashed later.
I'm installing Apache to see if I can reproduce the problem/fix it.
[2002-05-16 09:07:01] [EMAIL PROTECTED]
Edin created a new php_domxml.dll with libxml2-2.4.21 compile d in.
It's available at
http://ftp.proventum.net/pub/php/win32/php_domxml.zip
Can you check that. But i fear, it doesn't help solve the problem :(
Please be aware, that append_child changed the meaning in 4.2.1. The
former append_child is now append_sibling, and append_child behaves
like the w3c likes it. But appending a sibling to the root node,
doesn't make really sense, but it souldn't crash PHP, either :)
I would be very glad, if someone with windows programming experience
could hunt down the problem.
chregu
[2002-05-15 17:50:13] [EMAIL PROTECTED]
FWIW, the sample script works ok using the latest HEAD under IIS in
debug mode...well, works is an approximation. It doesn't crash until
the Zend tries to clean up memory, and then crashes in _zval_ptr_dtor.
Not feeling like a Zend guru today, I don't feel like attacking it.
I'll try Apache though to see if I can narrow this bug down.
[2002-05-15 16:15:27] [EMAIL PROTECTED]
I tried the newest xml-lib build from
http://www.fh-frankfurt.de/~igor/projects/libxml/ (Version 2.4.21) and
apache still crashes.
I also can confirm the barrier with 128 elements.
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/16888
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
even with the new php_domxml.dll it still crashes
also when you use the correct new function
append_sibling() it still crashes, even worser when you forget to add
content to your nodes as in the example above apache crashes in a loop
until the timeout is reached and no output reaches the browser.
create_element("HTML");
$root = $doc->append_child($root);
$body = $doc->create_element("element");
$body = $root->append_child($body);
//$body->set_content("content");
for($i = 1; $i < 130; $i++){
$element = $doc->create_element("element");
//$element->set_content("content ".$i);
$body->append_sibling($element);
}
echo htmlentities($doc->dump_mem(true));
?>
Previous Comments:
[2002-05-16 11:06:57] [EMAIL PROTECTED]
I'm looking into it. No guarantees though. I tried it with IIS, and
it seemed to work ok (Well the domxml part), it just crashed later.
I'm installing Apache to see if I can reproduce the problem/fix it.
[2002-05-16 09:07:01] [EMAIL PROTECTED]
Edin created a new php_domxml.dll with libxml2-2.4.21 compile d in.
It's available at
http://ftp.proventum.net/pub/php/win32/php_domxml.zip
Can you check that. But i fear, it doesn't help solve the problem :(
Please be aware, that append_child changed the meaning in 4.2.1. The
former append_child is now append_sibling, and append_child behaves
like the w3c likes it. But appending a sibling to the root node,
doesn't make really sense, but it souldn't crash PHP, either :)
I would be very glad, if someone with windows programming experience
could hunt down the problem.
chregu
[2002-05-15 17:50:13] [EMAIL PROTECTED]
FWIW, the sample script works ok using the latest HEAD under IIS in
debug mode...well, works is an approximation. It doesn't crash until
the Zend tries to clean up memory, and then crashes in _zval_ptr_dtor.
Not feeling like a Zend guru today, I don't feel like attacking it.
I'll try Apache though to see if I can narrow this bug down.
[2002-05-15 16:15:27] [EMAIL PROTECTED]
I tried the newest xml-lib build from
http://www.fh-frankfurt.de/~igor/projects/libxml/ (Version 2.4.21) and
apache still crashes.
I also can confirm the barrier with 128 elements.
[2002-05-15 12:28:24] [EMAIL PROTECTED]
One more interesting remark - DOM XML module crashes if more then 128
elements are created. Less then 128 elements are created without
problems. Maybe it will help you somehow?
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/16888
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: I'm looking into it. No guarantees though. I tried it with IIS, and it seemed to work ok (Well the domxml part), it just crashed later. I'm installing Apache to see if I can reproduce the problem/fix it. Previous Comments: [2002-05-16 09:07:01] [EMAIL PROTECTED] Edin created a new php_domxml.dll with libxml2-2.4.21 compile d in. It's available at http://ftp.proventum.net/pub/php/win32/php_domxml.zip Can you check that. But i fear, it doesn't help solve the problem :( Please be aware, that append_child changed the meaning in 4.2.1. The former append_child is now append_sibling, and append_child behaves like the w3c likes it. But appending a sibling to the root node, doesn't make really sense, but it souldn't crash PHP, either :) I would be very glad, if someone with windows programming experience could hunt down the problem. chregu [2002-05-15 17:50:13] [EMAIL PROTECTED] FWIW, the sample script works ok using the latest HEAD under IIS in debug mode...well, works is an approximation. It doesn't crash until the Zend tries to clean up memory, and then crashes in _zval_ptr_dtor. Not feeling like a Zend guru today, I don't feel like attacking it. I'll try Apache though to see if I can narrow this bug down. [2002-05-15 16:15:27] [EMAIL PROTECTED] I tried the newest xml-lib build from http://www.fh-frankfurt.de/~igor/projects/libxml/ (Version 2.4.21) and apache still crashes. I also can confirm the barrier with 128 elements. [2002-05-15 12:28:24] [EMAIL PROTECTED] One more interesting remark - DOM XML module crashes if more then 128 elements are created. Less then 128 elements are created without problems. Maybe it will help you somehow? [2002-05-15 12:23:10] [EMAIL PROTECTED] Confirmed under windows 2000 server running as CGI with following combinations: PHP 4.1.1 + libxml2 2.4.21 - works well PHP 4.2.0 + libxml2 2.4.21 - crash PHP 4.2.1 + libxml2 2.4.9 - crash Unfortunatelly latest PHP version - 4.2.1 have been build with libxml2 compiled as static library, so i can't test it with latest libxml2. So it is not a problem of libxml2, but something into DOM XML module itself. PHP crashes into final stage, when script execution itself is completed (and even function, registered as shutdown function have been executed). 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: Edin created a new php_domxml.dll with libxml2-2.4.21 compile d in. It's available at http://ftp.proventum.net/pub/php/win32/php_domxml.zip Can you check that. But i fear, it doesn't help solve the problem :( Please be aware, that append_child changed the meaning in 4.2.1. The former append_child is now append_sibling, and append_child behaves like the w3c likes it. But appending a sibling to the root node, doesn't make really sense, but it souldn't crash PHP, either :) I would be very glad, if someone with windows programming experience could hunt down the problem. chregu Previous Comments: [2002-05-15 17:50:13] [EMAIL PROTECTED] FWIW, the sample script works ok using the latest HEAD under IIS in debug mode...well, works is an approximation. It doesn't crash until the Zend tries to clean up memory, and then crashes in _zval_ptr_dtor. Not feeling like a Zend guru today, I don't feel like attacking it. I'll try Apache though to see if I can narrow this bug down. [2002-05-15 16:15:27] [EMAIL PROTECTED] I tried the newest xml-lib build from http://www.fh-frankfurt.de/~igor/projects/libxml/ (Version 2.4.21) and apache still crashes. I also can confirm the barrier with 128 elements. [2002-05-15 12:28:24] [EMAIL PROTECTED] One more interesting remark - DOM XML module crashes if more then 128 elements are created. Less then 128 elements are created without problems. Maybe it will help you somehow? [2002-05-15 12:23:10] [EMAIL PROTECTED] Confirmed under windows 2000 server running as CGI with following combinations: PHP 4.1.1 + libxml2 2.4.21 - works well PHP 4.2.0 + libxml2 2.4.21 - crash PHP 4.2.1 + libxml2 2.4.9 - crash Unfortunatelly latest PHP version - 4.2.1 have been build with libxml2 compiled as static library, so i can't test it with latest libxml2. So it is not a problem of libxml2, but something into DOM XML module itself. PHP crashes into final stage, when script execution itself is completed (and even function, registered as shutdown function have been executed). [2002-05-15 08:57:08] [EMAIL PROTECTED] I would blame libxml2 :) Do you have the latest libxml2 dll? (available anywhere from http://www.xmlsoft.org). Can you check with that? chregu 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: FWIW, the sample script works ok using the latest HEAD under IIS in debug mode...well, works is an approximation. It doesn't crash until the Zend tries to clean up memory, and then crashes in _zval_ptr_dtor. Not feeling like a Zend guru today, I don't feel like attacking it. I'll try Apache though to see if I can narrow this bug down. Previous Comments: [2002-05-15 16:15:27] [EMAIL PROTECTED] I tried the newest xml-lib build from http://www.fh-frankfurt.de/~igor/projects/libxml/ (Version 2.4.21) and apache still crashes. I also can confirm the barrier with 128 elements. [2002-05-15 12:28:24] [EMAIL PROTECTED] One more interesting remark - DOM XML module crashes if more then 128 elements are created. Less then 128 elements are created without problems. Maybe it will help you somehow? [2002-05-15 12:23:10] [EMAIL PROTECTED] Confirmed under windows 2000 server running as CGI with following combinations: PHP 4.1.1 + libxml2 2.4.21 - works well PHP 4.2.0 + libxml2 2.4.21 - crash PHP 4.2.1 + libxml2 2.4.9 - crash Unfortunatelly latest PHP version - 4.2.1 have been build with libxml2 compiled as static library, so i can't test it with latest libxml2. So it is not a problem of libxml2, but something into DOM XML module itself. PHP crashes into final stage, when script execution itself is completed (and even function, registered as shutdown function have been executed). [2002-05-15 08:57:08] [EMAIL PROTECTED] I would blame libxml2 :) Do you have the latest libxml2 dll? (available anywhere from http://www.xmlsoft.org). Can you check with that? chregu [2002-05-14 17:03:16] [EMAIL PROTECTED] Same error still occurs with PHP 4.2.1 Version 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: I tried the newest xml-lib build from http://www.fh-frankfurt.de/~igor/projects/libxml/ (Version 2.4.21) and apache still crashes. I also can confirm the barrier with 128 elements. Previous Comments: [2002-05-15 12:28:24] [EMAIL PROTECTED] One more interesting remark - DOM XML module crashes if more then 128 elements are created. Less then 128 elements are created without problems. Maybe it will help you somehow? [2002-05-15 12:23:10] [EMAIL PROTECTED] Confirmed under windows 2000 server running as CGI with following combinations: PHP 4.1.1 + libxml2 2.4.21 - works well PHP 4.2.0 + libxml2 2.4.21 - crash PHP 4.2.1 + libxml2 2.4.9 - crash Unfortunatelly latest PHP version - 4.2.1 have been build with libxml2 compiled as static library, so i can't test it with latest libxml2. So it is not a problem of libxml2, but something into DOM XML module itself. PHP crashes into final stage, when script execution itself is completed (and even function, registered as shutdown function have been executed). [2002-05-15 08:57:08] [EMAIL PROTECTED] I would blame libxml2 :) Do you have the latest libxml2 dll? (available anywhere from http://www.xmlsoft.org). Can you check with that? chregu [2002-05-14 17:03:16] [EMAIL PROTECTED] Same error still occurs with PHP 4.2.1 Version [2002-05-09 18:00:22] [EMAIL PROTECTED] Checked under Win98 and crashes if too many nodes are created. This is confirmed. 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888 Updated by: [EMAIL PROTECTED] Reported By: [EMAIL PROTECTED] Status: Feedback Bug Type: DOM XML related Operating System: Windows XP PHP Version: 4.2.0 New Comment: One more interesting remark - DOM XML module crashes if more then 128 elements are created. Less then 128 elements are created without problems. Maybe it will help you somehow? Previous Comments: [2002-05-15 12:23:10] [EMAIL PROTECTED] Confirmed under windows 2000 server running as CGI with following combinations: PHP 4.1.1 + libxml2 2.4.21 - works well PHP 4.2.0 + libxml2 2.4.21 - crash PHP 4.2.1 + libxml2 2.4.9 - crash Unfortunatelly latest PHP version - 4.2.1 have been build with libxml2 compiled as static library, so i can't test it with latest libxml2. So it is not a problem of libxml2, but something into DOM XML module itself. PHP crashes into final stage, when script execution itself is completed (and even function, registered as shutdown function have been executed). [2002-05-15 08:57:08] [EMAIL PROTECTED] I would blame libxml2 :) Do you have the latest libxml2 dll? (available anywhere from http://www.xmlsoft.org). Can you check with that? chregu [2002-05-14 17:03:16] [EMAIL PROTECTED] Same error still occurs with PHP 4.2.1 Version [2002-05-09 18:00:22] [EMAIL PROTECTED] Checked under Win98 and crashes if too many nodes are created. This is confirmed. [2002-04-28 17:37:34] [EMAIL PROTECTED] Seems to be an OS-specific problem. It is not reproducable under linux. Even with adding 100'000 nodes :) Can someone with access to windows please check that? chregu 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/16888 -- Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Feedback
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
Confirmed under windows 2000 server running as CGI with following
combinations:
PHP 4.1.1 + libxml2 2.4.21 - works well
PHP 4.2.0 + libxml2 2.4.21 - crash
PHP 4.2.1 + libxml2 2.4.9 - crash
Unfortunatelly latest PHP version - 4.2.1 have been build with libxml2
compiled as static library, so i can't test it with latest libxml2.
So it is not a problem of libxml2, but something into DOM XML module
itself.
PHP crashes into final stage, when script execution itself is
completed (and even function, registered as shutdown function have been
executed).
Previous Comments:
[2002-05-15 08:57:08] [EMAIL PROTECTED]
I would blame libxml2 :) Do you have the latest libxml2 dll? (available
anywhere from http://www.xmlsoft.org). Can you check with that?
chregu
[2002-05-14 17:03:16] [EMAIL PROTECTED]
Same error still occurs with PHP 4.2.1 Version
[2002-05-09 18:00:22] [EMAIL PROTECTED]
Checked under Win98 and crashes if too many nodes are created. This is
confirmed.
[2002-04-28 17:37:34] [EMAIL PROTECTED]
Seems to be an OS-specific problem. It is not reproducable under linux.
Even with adding 100'000 nodes :) Can someone with access to windows
please check that?
chregu
[2002-04-28 15:37:25] [EMAIL PROTECTED]
System: Apache/1.3.24 PHP running as SAPI-module (Binary from php.net)
simple script, which causes segfault
add_root("document");
for($i = 1; $i < 1000; $i++){
$element = $doc->create_element("element");
$element->set_content("content ".$i);
$root->append_child($element);
}
$xml = $doc->dumpmem();
echo htmlspecialchars($xml);
?>
Description:
the content is shown shortly in the browser, but apache causes a
segfault in module php4ts.dll at offset 00096057 and finally a 404
page is displayed.
This code causes no problems with PHP 4.1.2. When you try to create
only 100 elements in this loop, it runs without any seg-faults. For
complex xmldocuments this bug makes it impossible to use domxml with
php 4.2.
Modules:
php_domxml, php_xslt, php_gd und mysql
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
-Status: Open
+Status: Feedback
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
I would blame libxml2 :) Do you have the latest libxml2 dll? (available
anywhere from http://www.xmlsoft.org). Can you check with that?
chregu
Previous Comments:
[2002-05-14 17:03:16] [EMAIL PROTECTED]
Same error still occurs with PHP 4.2.1 Version
[2002-05-09 18:00:22] [EMAIL PROTECTED]
Checked under Win98 and crashes if too many nodes are created. This is
confirmed.
[2002-04-28 17:37:34] [EMAIL PROTECTED]
Seems to be an OS-specific problem. It is not reproducable under linux.
Even with adding 100'000 nodes :) Can someone with access to windows
please check that?
chregu
[2002-04-28 15:37:25] [EMAIL PROTECTED]
System: Apache/1.3.24 PHP running as SAPI-module (Binary from php.net)
simple script, which causes segfault
add_root("document");
for($i = 1; $i < 1000; $i++){
$element = $doc->create_element("element");
$element->set_content("content ".$i);
$root->append_child($element);
}
$xml = $doc->dumpmem();
echo htmlspecialchars($xml);
?>
Description:
the content is shown shortly in the browser, but apache causes a
segfault in module php4ts.dll at offset 00096057 and finally a 404
page is displayed.
This code causes no problems with PHP 4.1.2. When you try to create
only 100 elements in this loop, it runs without any seg-faults. For
complex xmldocuments this bug makes it impossible to use domxml with
php 4.2.
Modules:
php_domxml, php_xslt, php_gd und mysql
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
Same error still occurs with PHP 4.2.1 Version
Previous Comments:
[2002-05-09 18:00:22] [EMAIL PROTECTED]
Checked under Win98 and crashes if too many nodes are created. This is
confirmed.
[2002-04-28 17:37:34] [EMAIL PROTECTED]
Seems to be an OS-specific problem. It is not reproducable under linux.
Even with adding 100'000 nodes :) Can someone with access to windows
please check that?
chregu
[2002-04-28 15:37:25] [EMAIL PROTECTED]
System: Apache/1.3.24 PHP running as SAPI-module (Binary from php.net)
simple script, which causes segfault
add_root("document");
for($i = 1; $i < 1000; $i++){
$element = $doc->create_element("element");
$element->set_content("content ".$i);
$root->append_child($element);
}
$xml = $doc->dumpmem();
echo htmlspecialchars($xml);
?>
Description:
the content is shown shortly in the browser, but apache causes a
segfault in module php4ts.dll at offset 00096057 and finally a 404
page is displayed.
This code causes no problems with PHP 4.1.2. When you try to create
only 100 elements in this loop, it runs without any seg-faults. For
complex xmldocuments this bug makes it impossible to use domxml with
php 4.2.
Modules:
php_domxml, php_xslt, php_gd und mysql
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
Checked under Win98 and crashes if too many nodes are created. This is
confirmed.
Previous Comments:
[2002-04-28 17:37:34] [EMAIL PROTECTED]
Seems to be an OS-specific problem. It is not reproducable under linux.
Even with adding 100'000 nodes :) Can someone with access to windows
please check that?
chregu
[2002-04-28 15:37:25] [EMAIL PROTECTED]
System: Apache/1.3.24 PHP running as SAPI-module (Binary from php.net)
simple script, which causes segfault
add_root("document");
for($i = 1; $i < 1000; $i++){
$element = $doc->create_element("element");
$element->set_content("content ".$i);
$root->append_child($element);
}
$xml = $doc->dumpmem();
echo htmlspecialchars($xml);
?>
Description:
the content is shown shortly in the browser, but apache causes a
segfault in module php4ts.dll at offset 00096057 and finally a 404
page is displayed.
This code causes no problems with PHP 4.1.2. When you try to create
only 100 elements in this loop, it runs without any seg-faults. For
complex xmldocuments this bug makes it impossible to use domxml with
php 4.2.
Modules:
php_domxml, php_xslt, php_gd und mysql
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
Bug #16888 Updated: domXML causes Segfault, when you create to many Nodes
ID: 16888
Updated by: [EMAIL PROTECTED]
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: DOM XML related
Operating System: Windows XP
PHP Version: 4.2.0
New Comment:
Seems to be an OS-specific problem. It is not reproducable under linux.
Even with adding 100'000 nodes :) Can someone with access to windows
please check that?
chregu
Previous Comments:
[2002-04-28 15:37:25] [EMAIL PROTECTED]
System: Apache/1.3.24 PHP running as SAPI-module (Binary from php.net)
simple script, which causes segfault
add_root("document");
for($i = 1; $i < 1000; $i++){
$element = $doc->create_element("element");
$element->set_content("content ".$i);
$root->append_child($element);
}
$xml = $doc->dumpmem();
echo htmlspecialchars($xml);
?>
Description:
the content is shown shortly in the browser, but apache causes a
segfault in module php4ts.dll at offset 00096057 and finally a 404
page is displayed.
This code causes no problems with PHP 4.1.2. When you try to create
only 100 elements in this loop, it runs without any seg-faults. For
complex xmldocuments this bug makes it impossible to use domxml with
php 4.2.
Modules:
php_domxml, php_xslt, php_gd und mysql
--
Edit this bug report at http://bugs.php.net/?id=16888&edit=1
