in reply to Re^2: Hard to Debug windows memory error
in thread Hard to Debug windows memory error

hotchiwawa Thank you for your suggestions.

At this point I would rather try and get StrawberryPerl64 to work or at least get some kind of coherent/small failing test case rather than/before I use a 32 bit StrawberryPerl

From a general memory standpoint I am not really budging the needle (~72M of RAM before dying) but I'm doing my checking in the task manager so there may or may not be a different result in perl. However based on my research this error code can occur (among other reasons) in windows when an attempt to access a memory location is made after the contents have been deleted. Currently I'm following up on fishmongers suggestions as well as looking into Devel::cst and Devel::SizeMe.

Update: it looks like Devel::cst and Devel::SizeMe are both Linux specific modules requiring execinfo.h Devel::cst in this case seemed very promising.

  • Comment on Re^3: Hard to Debug windows memory error

Replies are listed 'Best First'.
Re^4: Hard to Debug windows memory error
by hotchiwawa (Scribe) on Jan 01, 2016 at 00:05 UTC
    Yep, good point with Devel::SizeMe and Devel::cst, thanks, I searched this kind of modules too :)

    Maybe you can also use autodie, to quit the application maybe before your current issue and get a possible source of the error...
    Edit: check Devel::Size, seems to have the same methods that Devel::SizeMe, but release in 2015 with less dependencies.