On Sat, 26 Feb 2005 11:20:43 +
Phil Thompson <[EMAIL PROTECTED]> wrote:
> Hopefully the attached shows that SIP 4.2 really, really doesn't have a
> memory
> leak.
>
Ok, after fixing the tests with the processEvents() qt-bugs suggestion, and your
clarifications about ownership parenting, I
On Monday 21 February 2005 3:12 pm, Nahuel Greco wrote:
> On Fri, 18 Feb 2005 23:51:46 +
>
> Phil Thompson <[EMAIL PROTECTED]> wrote:
> > I see the memory leak in the test_py_leak.py, but it's what I would
> > expect given what the script does. Because QDialog has a parent,
> > ownership (ie. r
On Fri, 18 Feb 2005 23:51:46 +
Phil Thompson <[EMAIL PROTECTED]> wrote:
> I see the memory leak in the test_py_leak.py, but it's what I would expect
> given what the script does. Because QDialog has a parent, ownership (ie.
> responsibility for destroying the QDialog) is transfered to the pa
On Thursday 17 February 2005 9:56 pm, Nahuel Greco wrote:
> On Thu, 17 Feb 2005 17:03:16 - (GMT)
>
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
> > Gentoo (x86 and amd64). I didn't run the C++ test - I was refering to the
> > original Python test that Torsten sent me.
>
> Ok, I was confused bec
On Thu, 17 Feb 2005 18:56:13 -0300
Nahuel Greco <[EMAIL PROTECTED]> wrote:
> Now I have the equivalent program done in C++ and PyQT, and the C++ one
> don't leak but the PyQT one keeps leaking. I'm attaching the new version
> of both and their output.
>
Note, the PyQT program leaks also when in
On Thu, 17 Feb 2005 17:03:16 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> Gentoo (x86 and amd64). I didn't run the C++ test - I was refering to the
> original Python test that Torsten sent me.
Ok, I was confused because I tought that you were having different results
with the C++ test
On Thursday 17 February 2005 19:22, Hans-Peter Jansen wrote:
>
> BTW, both SuSE 9.0 and 9.2 leaks like hell with your c++ test..
> Qt 3.3.4 still compiling ;-)
and did it only slightly better (-10MB at 10 dialogs: still 151 MB
compared to 3.2.1)
Pete
Hi Nahuel,
On Thursday 17 February 2005 17:32, Nahuel Greco wrote:
> On Thu, 17 Feb 2005 12:56:57 - (GMT)
>
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
> > > Do you tried the previous test program with Qt 3.3.4?
> >
> > Yes.
>
> I tried with Qt 3.3.4 and I have the same problem, and every per
> On Thu, 17 Feb 2005 12:56:57 - (GMT)
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
>
>> > Do you tried the previous test program with Qt 3.3.4?
>>
>> Yes.
>
> I tried with Qt 3.3.4 and I have the same problem, and every person I know
> with a Debian distribution and Qt 3.3.3 have the same erro
On Thu, 17 Feb 2005 12:56:57 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> > Do you tried the previous test program with Qt 3.3.4?
>
> Yes.
I tried with Qt 3.3.4 and I have the same problem, and every person I know
with a Debian distribution and Qt 3.3.3 have the same error, so maybe
> On Thu, 17 Feb 2005 09:24:36 - (GMT)
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
>
>> Qt 3.3.4 from Trolltech.
>
> Ok, maybe this is a problem related to Qt 3.3.3, I will try using Qt
> 3.3.4.
>
> Do you tried the previous test program with Qt 3.3.4?
Yes.
> There where no
> leaks?
I don't
On Thu, 17 Feb 2005 09:24:36 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> Qt 3.3.4 from Trolltech.
Ok, maybe this is a problem related to Qt 3.3.3, I will try using Qt 3.3.4.
Do you tried the previous test program with Qt 3.3.4? There where no leaks?
Saludos,
Nahuel Greco.
__
> On Wed, 16 Feb 2005 15:00:52 - (GMT)
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
>
>> What version of Qt are you using? There was some talk of the Debian
>> version of Qt leaking memory.
>
> I'm using the latest Qt-mt library from Debian unstable, 3.3.3
> (3:3.3.3-8).
> What version are you
On Wed, 16 Feb 2005 15:00:52 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> What version of Qt are you using? There was some talk of the Debian
> version of Qt leaking memory.
I'm using the latest Qt-mt library from Debian unstable, 3.3.3 (3:3.3.3-8).
What version are you using?
I'm at
> On Mon, 14 Feb 2005 17:13:56 - (GMT)
> "Phil Thompson" <[EMAIL PROTECTED]> wrote:
>
>> Although I haven't done anything specific to fix it, I have been unable
>> to
>> reproduce it with your script. Please try it and let me know.
>
> I compiled and installed the latest snapshot of SIP and PyQ
On Mon, 14 Feb 2005 17:13:56 - (GMT)
"Phil Thompson" <[EMAIL PROTECTED]> wrote:
> Although I haven't done anything specific to fix it, I have been unable to
> reproduce it with your script. Please try it and let me know.
I compiled and installed the latest snapshot of SIP and PyQT but the pro
On Mon, Feb 14, 2005 at 12:29:18PM -0300, Nahuel Greco wrote:
> On Fri, 11 Feb 2005 19:04:19 +
> Phil Thompson <[EMAIL PROTECTED]> wrote:
>
> > I would appreciate it if anybody who experienced problems with v4.2rc1
> > would
> > let me know that those problems have now been fixed.
> >
>
>
> On Fri, 11 Feb 2005 19:04:19 +
> Phil Thompson <[EMAIL PROTECTED]> wrote:
>
>> I would appreciate it if anybody who experienced problems with v4.2rc1
>> would
>> let me know that those problems have now been fixed.
>>
>
> I think I found a big memory leak in the PyQT version that is packaged
On Fri, 11 Feb 2005 19:04:19 +
Phil Thompson <[EMAIL PROTECTED]> wrote:
> I would appreciate it if anybody who experienced problems with v4.2rc1 would
> let me know that those problems have now been fixed.
>
I think I found a big memory leak in the PyQT version that is packaged with
Debian,
SIP v4.2rc2 has been released and is available from the usual place. There are
no known outstanding issues.
You will need to re-build PyQt, PyKDE etc if you are upgrading from v4.1.1 or
earlier. If you are using pyuic generated code then you will need a current
PyQt snapshot and re-run pyuic.
20 matches
Mail list logo
