blocks|key|3703118|text|我一点也不了解expat，但我猜出于某种原因，它必须在内存中保存太多的状态。XML+mal是以某种方式形成的吗？你有为大块的结束标记注册的处理程序吗？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3703119|我在想，如果你有一个为大块的末尾注册的处理程序，而expat期望将块传递给处理程序，那么expat可能在它能够完全收集该块之前就耗尽了内存。就像我说的，我不认识外国人，所以这可能是不可能的，我只是问问。|3703120|或者，您确定expat是内存丢失的地方吗？我可以想象这样一种情况:您保存了一些关于XML文件内容和您自己的数据结构的信息，或者是因为数据太大，或者是因为代码中的内存泄漏导致了内存不足的情况。|3703121|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I don't know expat at all, but I'd guess that it's having to hold too much state in memory for some reason. Is the XML mal formed in some way? Do you have handlers registered for end tags of large blocks? 

I'm thinking that if you have a handler registered for the end of a large block, and expat is expected to pass the block to the handler, then expat could be running out of memory before it's able to completely gather that block. As I said, I don't know expat, so this might not be possible, I'm just asking.

Alternately, are you sure that expat is where the memory loss is? I could imagine a situation where you were keeping some information about the contents of the XML file, and your own data structures, either because the data was so large, or because of memory leaks in your code, caused the out of memory condition.

blocks|key|484210|text|我以前使用expat解析过大文件，从来没有遇到过任何问题。我假设您使用的是SAX，而不是expat+DOM包装器。如果您使用的是DOM，那么这就是您的问题所在--它本质上是试图将整个文件加载到内存中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|484211|您是否在解析XML时分配对象，而不是释放它们？这将是我要检查的第一件事。检查问题是否真的与expat有关的一种方法是-如果您将程序简化为具有空标记处理程序的简单版本(即，它只解析文件，而不对结果做任何操作)，它仍然会耗尽内存吗？|484212|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I've used expat to parse large files before and never had any problems. I'm assuming you're using SAX and not one of the expat DOM wrappers. If you are using DOM, then that's your problem right there - it would be essentially trying to load the whole file into memory.

Are you allocating objects as you parse the XML and maybe not deallocating them? That would be the first thing I would check for. One way to check if the problem is really with expat or not - if you reduce the program to a simple version that has empty tag handlers (i.e. it just parses the file and does nothing with the results) does it still run out of memory?

blocks|key|3703217|text|Expat是一个事件驱动的解析器，它不会构造大的内存结构。所以它可能不是expat+(它被广泛用于解析大文件)是问题所在--它更有可能是您自己的代码。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3703218|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Expat is an event-driven parser which does not construct large in-memory structures. So it's probably not expat (which is very widely used for parsing large files) that is the problem - much more likely it is your own code.

blocks|key|484310|text|Expat有漏洞-我已经开始在一个长时间运行的服务器中使用它，我发现无论解析器是否被释放，它总是会泄漏内存。较新版本的xmlparse.c不能解决此问题，只能隐藏现有泄漏。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|484311|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Expat has leaks - I've started using it in a long-running server, and am finding that it consistently leaks memory, whether the parser is freed or not. More recent versions of xmlparse.c do not resolve this problem, only hide existing leaks.

I am using expat parser to parse an XML file of around 15 GB . The problem is it throws an "Out of Memory" error and the program aborts .

I want to know has any body faced a similar issue with the expat parser or is it a known bug and has been rectified in later versions ?

expat parser: memory consumption

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在使用expat解析器解析一个大约15 GB的XML文件。问题是它抛出一个“内存不足”错误，程序中止。我想知道有没有什么机构遇到过类似的问题，或者它是一个已知的bug，并在后来的版本中得到了纠正？

问expat解析器:内存消耗
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问expat解析器:内存消耗EN