Mark Dootson 09.09.2009 17:30: > I'm not entirely certain this is really a Wx::Perl::ProcessStream issue.
Hi Mark. Thanks for the quick reply! Yep, sorry, I did not mean to blame this on Wx::Perl::ProcessStream. $subject =~ s/in /using / ... In fact, I am fairly certain that there is nothing obvious in the code of Wx::Perl::ProcessStream that could explain the leak. In my application I actually use GetStdOutBuffer()/GetStdErrBuffer(). Using these methods in the sample I posted before does not have any noticable effect on memory consumption. > For sure, it is Wx::Perl::ProcessStream consuming the memory. I am not > sure it is a fault in Wx::Perl::ProcessStream that causes perl to > allocate additional memory when additional processes are run. Having spent some hours with this problem, I now suspect that there the problem lurks at some lower layer, maybe in the XS-parts of Wx or even wxWidgets itself. Alas, I simply lack the skills to debug those. > I will have to run some tests at some point to confirm this or fix problem. Having confirmation that this behaviour is not just a whim of my specific setup (perl/Wx/wxWidgets) would really help. If it isn't, I'll have to either look into alternative approaches or hope for a bug-fix ... -Cornelius
