Bug #79642 [Opn]: xml_parse() fails with XML_ERROR_NO_MEMORY with a mere 17M file
| From: | php4fan at gmail dot com | Date: | Sat, 22 Jan 2022 15:30:36 +0000 |
| Subject: | Bug #79642 [Opn]: xml_parse() fails with XML_ERROR_NO_MEMORY with a mere 17M file | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-239224@lists.php.net to get a copy of this message | ||
Edit report at https://bugs.php.net/bug.php?id=79642&edit=1
ID: 79642
User updated by: php4fan at gmail dot com
Reported by: php4fan at gmail dot com
Summary: xml_parse() fails with XML_ERROR_NO_MEMORY with a
mere 17M file
Status: Open
Type: Bug
Package: *XML functions
Operating System: debian
PHP Version: 7.2.31
Block user comment: N
Private report: N
New Comment:
What is "block user comments" supposed to accomplish? I see the spammers are spamming
anyway.
Previous Comments:
------------------------------------------------------------------------
[2022-01-22 15:19:06] glint dot post2022 at gmail dot com
https://glintpost.com/wooden-food-toys/
------------------------------------------------------------------------
[2022-01-22 15:18:30] glint dot post2022 at gmail dot com
https://pluto-mart.net/river-rock-epoxy-table/
------------------------------------------------------------------------
[2022-01-22 14:05:16] glint dot post2022 at gmail dot com
https://glintpost.com/basket-plant-stand/
------------------------------------------------------------------------
[2022-01-22 14:04:37] glint dot post2022 at gmail dot com
https://pluto-mart.net/heartfelt-memory-lamps/
------------------------------------------------------------------------
[2020-05-27 16:51:01] cmb@php.net
> why can't parse_xml() do it internally, by the way?
Well, it could, but you'd still have to provide the full XML as
string, what might be wasteful. In my opinion, xml_parse_stream()
would be nice to have, but on the other hand, that can easily be
written in userland as well.
------------------------------------------------------------------------
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
https://bugs.php.net/bug.php?id=79642
--
Edit this bug report at https://bugs.php.net/bug.php?id=79642&edit=1