| Subject: | Segfault on Wx::PlThreadEvent destruction |
The following code is from Padre::Wx::Role::Conduit.
It seems to show that on rare occasions thread events can explode when
they fall out of scope and are destroyed (at least, that's my assumption
since the $_[1] param is always a plain string).
It does not happen often, but the Find in Files background thread in
Padre produces hundreds or thousands of thread events.
sub signal {
if ($CONDUIT) {
$CONDUIT->AddPendingEvent(
Wx::PlThreadEvent->new( -1, $SIGNAL, $_[1] )
);
}
return 1;
# NOTE: Crashes like the following have been observed.
#
# Free to wrong pool 8d60100 not 963e10 at
# C:/strawberry/perl/site/lib/Padre/Wx/Role/Conduit.pm line 153.
# Attempt to free unreferenced scalar: SV 0x2099354,
# Perl interpreter: 0x4f2c2b4
# at C:/strawberry/perl/site/lib/Padre/Wx/Role/Conduit.pm line 153.
#
# It appears that the destruction of the Wx::PlThreadEvent can
# cause segfaults in some situations.
}