in reply to Re^2: perl is crashing due to memory leak when the template toolkit output is being dumped into an output file(xml file)
in thread perl is crashing due to memory leak when the template toolkit output is being dumped into an output file(xml file)

Okay, that's the first part.

Can you also post the output of this: systeminfo | findstr /C:Physical

Also curious what code/module isn't working in 64 bit Perl...

  • Comment on Re^3: perl is crashing due to memory leak when the template toolkit output is being dumped into an output file(xml file)

Replies are listed 'Best First'.
Re^4: perl is crashing due to memory leak when the template toolkit output is being dumped into an output file(xml file)
by kimya8 (Novice) on Jan 03, 2019 at 12:19 UTC

    Total Physical Memory: 32,689 MB Available Physical Memory: 23,282 MB The code that does not work is another code written elsewhere(again perl), but it is time consuming to get that working And i am unable to shorten the template file to get to a stage where it will be working. Thanks for all the help though. Really appreciate.

[reply]

      Note that your 32-bit Perl can, on Windows, at most address 4GB of memory. Most likely it can only address 2GB of memory.

      Upgrading to 5.28 (or a more recent version of Perl) from http://strawberryperl.com/ will allow you to address more memory if you install a 64bit version.

[reply]

      Sounds like 32bit Perl on 64 bit Windows then?

      You could try the trick outlined in this node: Memory usage in Perl on Windows systems to get 3GB available for Perl instead of 2GB. It's a workaround, but might help you until the data and/or template get bigger.

[reply]

In Section Seekers of Perl Wisdom