Re: "Free to wrong pool" error. (hints)

"Out of memory!" makes no sense for that code. It seems clear to me that Perl's Ctrl-C handler (for Windows) is having a very hard time. "Free to wrong pool 2f4d50 not 1000 during global destruction" makes no sense since you aren't using threads. But that bit of hex translates to "/MP" so something is overwriting memory that it shouldn't be.

- tye

Comment on Re: "Free to wrong pool" error. (hints)

Replies are listed 'Best First'.
Re^2: "Free to wrong pool" error. (hints) by davido (Cardinal) on Oct 10, 2011 at 00:24 UTC
Thanks for the tips, tye. I had a feeling that the CTRL-C wasn't being handled gracefully. As I fiddle, any time my code retains the `last OUTER;`, where it jumps from an inner loop to the outer loop, I get the behavior. So maybe the error messages that mention scope are on to something. I do wish I could reproduce it in a way where a test could be written that would demonstrate it reliably. Dave	[reply] [d/l]

Replies are listed 'Best First'.

Re^2: "Free to wrong pool" error. (hints)
by davido (Cardinal) on Oct 10, 2011 at 00:24 UTC

Thanks for the tips, tye. I had a feeling that the CTRL-C wasn't being handled gracefully. As I fiddle, any time my code retains the last OUTER;, where it jumps from an inner loop to the outer loop, I get the behavior. So maybe the error messages that mention scope are on to something.

I do wish I could reproduce it in a way where a test could be written that would demonstrate it reliably.

Dave

[reply]
[d/l]