Hi,
The real issue is in
cpp/v_cback.cpp
and the method.
bool wxPliVirtualCallback::FindCallback( pTHX_ const char* name ) const
Failure to find a callback in the base Perl class here causes an SV leak
as measured by Devel::Leak;
So, a basic fix for the problem in Wx::Timer was to add the method to
the base Perl class.
I really need to fix wxPliVirtualCallback::FindCallback( pTHX_ const
char* name ) const properly but the addition of wxTimer::Notify clears
the issue for Wx::Timer for now.
Regards
Mark
On 03/01/2016 17:52, Steve Cookson - gmail wrote:
Hi Mark,
Happy New Year.
Great that you fixed this. Thanks very much. I looked at code and I
didn't understand. It seems that you've added a wxTimer::Notify event.
But I don't understand why this should cause a memory leak. Weird. Was
there a problem with the undertlying wxWidgets as well?
I haven't tested the fix yet, but I assume it works, could you explain
please why this caused an error?
Regards,
Steve.
On 20/12/15 18:26, Mark Dootson wrote:
Hi,
Wx 0.9928 has been released to CPAN.
This fixes a Wx::Timer memory leak.
Regards
Mark
