On Wednesday 23 March 2011 05:41:14 anatoly techtonik wrote: > I wonder if it is possible to detect such memory leaks when running test > suite? -- > anatoly t.
Me too... but running the Python interpreter under valgrind gives *a lot* of false positives. BTW, I failed to reproduce the bug 763 [1] with latest code from git. [1] http://bugs.pyside.org/show_bug.cgi?id=763 > On Sun, Mar 20, 2011 at 1:34 PM, Matti Airas <[email protected]> wrote: > > Hi Ranen, > > > > thanks, I filed a bug against the issue: > > > > http://bugs.pyside.org/show_bug.cgi?id=763 > > > > To follow the bug resolution progress, add yourself as a CC to the bug. > > > > Cheers, > > > > ma. > > > > On 19 March 2011 19:11, Ranen Ghosh <[email protected]> wrote: > >> In fact, I suspect that there is always a memory leak when calling > >> QPixmap's constructor, but that in some cases it is not noticed because > >> some form of optimization is preventing QPixmap construction when it is > >> superfluous. > >> > >> Note that the following code in the timer callback causes a memory > >> blow-up, but simply switching the pxmp assignment statements, and > >> leaving everything else as-is, results in no memory blow-up. > >> > >> img = QtGui.QImage('tiger.png') > >> fd, pathname = tempfile.mkstemp('.bmp') > >> os.close(fd) > >> img.save(pathname, "BMP") > >> pxmp = QtGui.QPixmap(pathname) > >> # pxmp = QtGui.QPixmap('tiger.png') > >> os.remove(pathname) > >> self.lbl.setPixmap(pxmp) > >> > >> Ranen > >> > >> On Fri, Mar 18, 2011 at 3:45 PM, Ranen Ghosh <[email protected]> wrote: > >>> Hi, I am noticing a memory leak with PySide's QPixmap.fromImage static > >>> method. > >>> Here is a small example program to demonstrate it: > >>> http://pastebin.com/VmKncUFY > >>> > >>> For the first 30 seconds or so, everything seems fine. At that point, > >>> my Xorg process's memory usage starts to shoot up at about 20M per > >>> second. > >>> > >>> The following info may be helpful: > >>> > >>> If I use the QPixmap's constructor with the filename as an argument, > >>> rather than using the static QPixmap.fromImage method, I don't observe > >>> the memory issue. > >>> > >>> If I don't call self.lbl.setPixmap(pxmp) , I don't observe the memory > >>> issue. > >>> > >>> If I double the timer delay, it takes roughly twice as long for the > >>> memory spike to happen. > >>> > >>> If I replace PySide with PyQt4 in the import statements, I do not > >>> observe this memory issue. > >>> > >>> Ranen > >> > >> _______________________________________________ > >> PySide mailing list > >> [email protected] > >> http://lists.pyside.org/listinfo/pyside > > > > _______________________________________________ > > PySide mailing list > > [email protected] > > http://lists.pyside.org/listinfo/pyside > > _______________________________________________ > PySide mailing list > [email protected] > http://lists.pyside.org/listinfo/pyside -- Hugo Parente Lima INdT - Instituto Nokia de Tecnologia
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ PySide mailing list [email protected] http://lists.pyside.org/listinfo/pyside
