I’ll presume that you are intending by the above to create a minimalistic example. But, we need details here: how large is this data structure? Are you running a 64-bit version of Perl? Do you have any idea as to the memory-footprint of this application prior to the step that generates the XML file? Is there any possibility at all of self-referential “loops” within this data structure, which might cause an algorithm to iterate endlessly? (Test::Memory::Cycle, and Devel::Cycle, can automatically look for these.)
Obviously, it is unreasonable to expect that a program running on a 32GB machine, dealing with a data structure that is thought to be about 1GB, and running 64-bit software in a 64-bit environment, would be encountering such issues. (Whereas, BTW, if the actual system were 32-bit, the total memory space would be less than 2GB, and overflow is a distinct possibility.) So, we really don’t have enough solid details here with which to offer many solutions . . . yet. I’m not yet persuaded that we should finger this particular package. Rather, I suspect that there is something else going on that we don’t yet see.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|