> I don't have those problems. How did you install PyQt? I use MacPorts (using
Python 2.7).
Arne,
thanks for the MacPorts tip. I have installed pyqt through MacPorts and it works
just fine. No memory leak anymore. After figuring out how to get through our
firewall and making the MacPorts python
Arne Schmitz gmx.net> writes:
>
> Am 27.01.2011 um 18:12 schrieb Danny Shevitz:
>
> > Any PyQt application generates the same message. If I run something from the
> > samples directory, I get the same memory leak, so it is nothing in my code.
>
> I don't have those problems. How did you instal
Am 27.01.2011 um 18:12 schrieb Danny Shevitz:
> Any PyQt application generates the same message. If I run something from the
> samples directory, I get the same memory leak, so it is nothing in my code.
I don't have those problems. How did you install PyQt? I use MacPorts (using
Python 2.7).
FWIW,
Any PyQt application generates the same message. If I run something from the
samples directory, I get the same memory leak, so it is nothing in my code.
thanks,
Danny
___
PyQt mailing listPyQt@riverbankcomputing.com
http://www.riverbankcomput
Howdy,
I have an app that works just fine on the one click windows distro.
I just tried to run the same app on a Mac for the first time. I am nobody's
Mac expert, but I did manage to get the latest PyQt4, Sip, QScintilla working.
When I run my app on the Mac, I get the following:
macshev:elm3
On Mon, 16 Aug 2010 22:59:22 + (UTC), danny wrote:
> thanks,
>
> your solution works, and stops my code from seg faulting. I'm curious
> why mine doesn't work. In the documentation for QMainWindow
>
>
http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/qmainwindow.html#addToolBar-3
>
thanks,
your solution works, and stops my code from seg faulting. I'm curious
why mine doesn't work. In the documentation for QMainWindow
http://www.riverbankcomputing.co.uk/static/Docs/PyQt4/html/qmainwindow.html#addToolBar-3
The third overloading of the addToolBar method, was what I was using.
On 16/08/10 18:27, danny wrote:
Howdy,
I have run into this curious problem that I think is caused by a memory leak
or improper reference counting related to toolbars in QMainWindow.removeToolBar.
The problem appears when you remove a toolbar but keep an instance variable
maintaining a reference
Howdy,
I have run into this curious problem that I think is caused by a memory leak
or improper reference counting related to toolbars in
QMainWindow.removeToolBar.
The problem appears when you remove a toolbar but keep an instance variable
maintaining a reference to the toolbar. I am aware that
On Sun, 2008-07-06 at 17:29 +0100, Phil Thompson wrote:
> On Sun, 06 Jul 2008 15:18:10 +0200, Giovanni Bajo <[EMAIL PROTECTED]>
> wrote:
> > On Sat, 2008-07-05 at 23:04 +0100, Phil Thompson wrote:
> >> On Thu, 03 Jul 2008 16:04:42 +0200, Giovanni Bajo <[EMAIL PROTECTED]>
> >> wrote:
> >> > Hi Phil,
On Sun, 06 Jul 2008 15:18:10 +0200, Giovanni Bajo <[EMAIL PROTECTED]>
wrote:
> On Sat, 2008-07-05 at 23:04 +0100, Phil Thompson wrote:
>> On Thu, 03 Jul 2008 16:04:42 +0200, Giovanni Bajo <[EMAIL PROTECTED]>
>> wrote:
>> > Hi Phil,
>> >
>> > with SIP 4.7.6, PyQt 4.2.2, Qt 4.4.0:
>> >
>> > ===
On Sat, 2008-07-05 at 23:04 +0100, Phil Thompson wrote:
> On Thu, 03 Jul 2008 16:04:42 +0200, Giovanni Bajo <[EMAIL PROTECTED]>
> wrote:
> > Hi Phil,
> >
> > with SIP 4.7.6, PyQt 4.2.2, Qt 4.4.0:
> >
> >
> > import sip
> > import weakref
> > from PyQt4.Qt
On Thu, 03 Jul 2008 16:04:42 +0200, Giovanni Bajo <[EMAIL PROTECTED]>
wrote:
> Hi Phil,
>
> with SIP 4.7.6, PyQt 4.2.2, Qt 4.4.0:
>
>
> import sip
> import weakref
> from PyQt4.Qt import *
>
> class MyWidget(QWidget):
> def sizeHint(self):
>
On Fri, 2008-07-04 at 10:48 +0200, Sundance wrote:
> Giovanni Bajo wrote:
>
> > The assert triggers, meaning that the object of type MyWidget is not
> > released.
>
> Hi Giovanni,
>
> Yes, this is a known bug: SIP keeps a hard reference to bound methods in
> its method cache (the bound method b
Giovanni Bajo wrote:
> The assert triggers, meaning that the object of type MyWidget is not
> released.
Hi Giovanni,
Yes, this is a known bug: SIP keeps a hard reference to bound methods in
its method cache (the bound method being ws.sizeHint in your example).
Since bound methods keep a refere
Hi Phil,
with SIP 4.7.6, PyQt 4.2.2, Qt 4.4.0:
import sip
import weakref
from PyQt4.Qt import *
class MyWidget(QWidget):
def sizeHint(self):
return QSize(900, 700)
app = QApplication([])
ws = MyWidget(None)
wr = weakref.ref(ws)
L = QVBoxLa
Hurray! Thanks to Justin Noel on the qt-interest list, the following
code now works and doesn't leak!
Noam
===
#!/usr/bin/env python
import sys
from PyQt4 import QtCore, QtGui
from PyQt4.QtCore import Qt
class TableModel(QtCore.QAbstractTableModel):
def rowCount(self, index):
On Sunday 23 December 2007, Noam Raphael wrote:
> 2007/12/23, Andreas Pakulat <[EMAIL PROTECTED]>:
> > Works fine here on Debian unstable, with a bit older PyQt4(I think from
> > November) and Qt4.3.2. Yes the memory usage increases when starting to
> > scroll, but not that much. After scrolling fr
2007/12/23, Andreas Pakulat <[EMAIL PROTECTED]>:
> Works fine here on Debian unstable, with a bit older PyQt4(I think from
> November) and Qt4.3.2. Yes the memory usage increases when starting to
> scroll, but not that much. After scrolling from one end to the other on
> both bars the python proces
On Sunday 23 December 2007, Noam Raphael wrote:
> 2007/12/23, Phil Thompson <[EMAIL PROTECTED]>:
> > > Is there anything that can be done?
> >
> > Not if I can't reproduce the problem. I'm using current SIP and PyQt
> > snapshots and Qt 4.3.3.
>
> It also works for me on windows, using the latest b
On 23.12.07 13:59:30, Noam Raphael wrote:
> 2007/12/23, Phil Thompson <[EMAIL PROTECTED]>:
> > > Is there anything that can be done?
> >
> > Not if I can't reproduce the problem. I'm using current SIP and PyQt
> > snapshots
> > and Qt 4.3.3.
> >
> It also works for me on windows, using the latest
2007/12/23, Phil Thompson <[EMAIL PROTECTED]>:
> > Is there anything that can be done?
>
> Not if I can't reproduce the problem. I'm using current SIP and PyQt snapshots
> and Qt 4.3.3.
>
It also works for me on windows, using the latest binary. But have you
tried it on linux? I'm using ubuntu 7.10
On Saturday 22 December 2007, Noam Raphael wrote:
> 2007/12/21, Phil Thompson <[EMAIL PROTECTED]>:
> > Works fine for me with current versions.
> >
> > Phil
>
> Ok, I now compiled by myself PyQt 4.3.3 with sip 4.7.3. I have qt
> 4.3.2 installed. The memory still leaks.
>
> Is there anything that ca
2007/12/21, Phil Thompson <[EMAIL PROTECTED]>:
> Works fine for me with current versions.
>
> Phil
Ok, I now compiled by myself PyQt 4.3.3 with sip 4.7.3. I have qt
4.3.2 installed. The memory still leaks.
Is there anything that can be done?
Noam
___
P
On Thursday 20 December 2007, Noam Raphael wrote:
> Hello,
>
> I created a simple program which uses QAbstractTableModel to display a
> table with 1000x1000 cells. It works, but if I enlarge the window and
> scroll a little bit the memory consumption of the program jumps to the
> skies (If I weren'
Hello,
I created a simple program which uses QAbstractTableModel to display a
table with 1000x1000 cells. It works, but if I enlarge the window and
scroll a little bit the memory consumption of the program jumps to the
skies (If I weren't careful, my system would have stuck.)
Here's the program.
On Wednesday 23 March 2005 3:51 pm, Nahuel Greco wrote:
> Hi, I think that I have found a memory leak in the latest PyQT snapshot.
> When you create forms, if the form constructor connects their signals,
> after his destruction a "weakref" object remains in memory. Note the
> attached logs:
>
>
Hi, I think that I have found a memory leak in the latest PyQT snapshot. When
you
create forms, if the form constructor connects their signals, after his
destruction
a "weakref" object remains in memory. Note the attached logs:
without_signal_connections.log: For this log I only pressed the
28 matches
Mail list logo
