You cannot call the ->DESTROY method yourself and expect anything sane to happen. It is only meant to be called when the object is *actually* being deallocated. If you do that then you'll need to somehow note in your object that its been "pre-destroyed". Your rebless idea has no bearing on this and is purely obfuscatory. Its no help, abandon it now.
Really though, you need to fix your code so you're not keeping extra references. I'll guess you've got other things leaking memory as well. I'd go through your code with a fine-tooth comb and consider whether you've created any cyclical references - perl's garbage collector won't clean those up for you. ($self->{foo} = $self)
sub DESTROY { my $self = shift; # Oops! I already destroyed myself return if exists $self->{_PRE_DESTROY}; $self->{_PRE_DESTROY} = 1; # Do whatever your cleanup action is. }
In reply to Re: explicitly calling destructor
by diotalevi
in thread explicitly calling destructor
by mla
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |