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 ob
I notice $event->GetProcess->Destroy should reset the buffer.
On Wed, Sep 9, 2009 at 10:00 PM, Mark Dootson wrote:
> Hi,
>
> I'm not entirely certain this is really a Wx::Perl::ProcessStream issue.
>
> For sure, it is Wx::Perl::ProcessStream consuming the memory. I am not sure
> it is a fault
Hi,
I'm not entirely certain this is really a Wx::Perl::ProcessStream issue.
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.
I will have to r
Hi there.
I have a question about Wx::Perl::ProcessStream and memory usage.
My background is a long running GUI application that (from time to time)
executes external commands, for example running rsync processes. In my GUI I'd
like to give some feedback about what is happening. My plan was to
