Re: Massive PerlQt memory leakage
Marius Kjeldahl <[email protected]> Wed, 06 Jul 2005 23:54:23 +0200
| Newsgroups | gmane.comp.kde.devel.perl |
|---|---|
| Message-ID | <[email protected]> |
Just an update; the patch certainly slowed down leakage alot, but it is still there. We've just completed a more or less line-for-line port to C++, and there we see no leakage. I would suspect more leakage in C++ (considering explicit memory management), but so far we have no leakage in the C++ version. So if you are going to create long running processes using PerlQt, you might want to do some benchmarking yourself first. Marius K. Gary Greene wrote: > On Tuesday 05 July 2005 06:00 am, Marius Kjeldahl wrote: > >>Gary Greene wrote: >> >>>I can confirm this as Germain sent me a patch for it a little over a year >>>ago when I packaged it for another distribution. The patch is attached. >>> >>> >>> >>>------------------------------------------------------------------------ >>> >>>--- PerlQt/Qt.xs~ 2004-06-01 10:12:35.000000000 +0100 >>>+++ PerlQt/Qt.xs 2004-06-01 10:12:35.000000000 +0100 >>>@@ -152,6 +152,7 @@ >>> SvREFCNT_dec(keysv); >>> return 0; >>> } >>>+ SvREFCNT_dec(keysv); >>> return *svp; >>> } >> >>Patch looks golden and seems to solve memory leakage at my end. I would >>suggest somebody with a clue puts out a new release with it included, to >>save others from struggling with leakage as we had to go through. >>Hopefully, Google will also pick this up. Not sure why I never found any >>references to it when I tried (and I searched a lot). >> >>Thanks, >> >>Marius K. >>_______________________________________________ >>Kde-perl mailing list >>[email protected] >>https://mail.kde.org/mailman/listinfo/kde-perl > > > Agreed, this should warrant at least a 3.0009 at least. > > > > ------------------------------------------------------------------------ > > _______________________________________________ > Kde-perl mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/kde-perl