in reply to Re^2: threads causing memory leak
in thread threads causing memory leak

No, i wait for it to finish.

That's exactly what join does. But if you don't join it, it's memory is never returned to the memory pool.

Free to wrong pool 9f2520 not 3f4e10

That's a bug in Win32::GUI.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^4: threads causing memory leak
by Proclus (Beadle) on Sep 12, 2010 at 11:29 UTC
    WxPerl Windows will probably crash too. I will test it when I have some time.
[reply]
      WxPerl Windows will probably crash too.

      Perhaps "bug" is too strong a term. Let's call it an "incompatibility".

      The problem as I understand it, is to with static data in XS modules on modules that were never designed to work with threads. I believe that it is impossible to correct this incompatibility from within threads.

      It requires modules like Win32::GUI, Tk (perhaps WxPerl), and many others, be modified to become compatible with threads.

      I have no experience of WxPerl, but I'd bet that the same techniques I use in Re: threads causing memory leak (No leak!) would work with it also.

      Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
      "Science is about questioning the status quo. Questioning authority".
      In the absence of evidence, opinion is indistinguishable from prejudice.
[reply]

      For the record, it's quite possible to use Wx with perl threads. Padre does it, for example.

[reply]
[reply]

In Section Seekers of Perl Wisdom