Re^8: Handling HUGE amounts of data

A little sleuthing indicates it's not a problem with scoping the variables. But I'm still digging.

The script is throwing the 'out of memory' after the output file is closed, after that entire subroutine has returned to main.

In fact, it's throwing the 'out of memory after dataout.pl has called the next script in the chain.

That would indicate it's throwing 'out of memory' during clean-up somewhere, right?

Or maybe it's doing it because it's on Windows.

Comment on Re^8: Handling HUGE amounts of data

Replies are listed 'Best First'.
Re^9: Handling HUGE amounts of data by BrowserUk (Patriarch) on Feb 01, 2011 at 00:05 UTC
I'd suggest that you add a line: `print 'Done'; <STDIN>;` just before the end of the program. When the prompt appears, pop up he task manager (or better, Process Explorer if you have it), and monitor the memory usage at that point. Then, leaving the manager window visible, hit enter on the command session and watch what happens. Personally, I've never seen the situation where 'out of memory' occurred during clean up, but that doesn't mean it couldn't happen. But the thing that is baffling me is why you are still running out of memory now you've reduced the memory usage? Perhaps now would be a good time to post the latest version of your code and see if other people (me) can reproduce your findings. Remember to include the initial input file--or sufficient information to allow us to accurately mock it up--so that we can run the code in a realistic fashion. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice.	[reply] [d/l]

Replies are listed 'Best First'.

Re^9: Handling HUGE amounts of data
by BrowserUk (Patriarch) on Feb 01, 2011 at 00:05 UTC

I'd suggest that you add a line: print 'Done'; <STDIN>; just before the end of the program. When the prompt appears, pop up he task manager (or better, Process Explorer if you have it), and monitor the memory usage at that point. Then, leaving the manager window visible, hit enter on the command session and watch what happens.

Personally, I've never seen the situation where 'out of memory' occurred during clean up, but that doesn't mean it couldn't happen.

But the thing that is baffling me is why you are still running out of memory now you've reduced the memory usage? Perhaps now would be a good time to post the latest version of your code and see if other people (me) can reproduce your findings.

Remember to include the initial input file--or sufficient information to allow us to accurately mock it up--so that we can run the code in a realistic fashion.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

[reply]
[d/l]