Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-30 Thread Andrew Suffield
On Mon, Apr 30, 2012 at 09:25:52AM +0200, Hans-Peter Jansen wrote: > following Eriks suggestion of disabling the GC altogether would have given a > valuable data point for your issue. Oh, I did try that. Everything works fine when GC is disabled. > Vanishing still referenced local > variables i

Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-30 Thread Hans-Peter Jansen
Dear Andrew, Am Sunday 29 April 2012 17:21:34 schrieb Andrew Suffield: > On Sun, Apr 29, 2012 at 03:51:43PM +0100, Phil Thompson wrote: > > You might try keeping explicit references to any objects involved in the > > query where you might be expecting PyQt to keep the reference for you. > > At the

Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-29 Thread Andrew Suffield
On Sun, Apr 29, 2012 at 03:51:43PM +0100, Phil Thompson wrote: > You might try keeping explicit references to any objects involved in the > query where you might be expecting PyQt to keep the reference for you. At the point when it gets collected, it's still in scope as a local variable of the pyt

Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-29 Thread Phil Thompson
On Sat, 28 Apr 2012 12:14:14 +0100, Andrew Suffield wrote: > On Sat, Apr 28, 2012 at 01:05:37PM +0200, Erik Janssens wrote: >> which version of PyQt are you using ? >> >> When in older versions (I think something like 2 releases ago), >> the garbage collection kicks in in a thread and it deletes

Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-28 Thread Erik Janssens
and are you sure the query is being garbage collected, and not something else ? I've noticed in the past that the garbage collector often kicks in right after a query or so. Probably because of some time that has passed or something like that. On Sat, 2012-04-28 at 12:14 +0100, Andrew Suffield

Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-28 Thread Adrian Buehlmann
On 2012-04-27 13:53, Andrew Suffield wrote: > query = QtSql.QSqlQuery() > if not query.prepare('select %s from %s where %s' % > (','.join(field_names), table, self.key_expr(table))): > > I get 'RuntimeError: underlying C/C++ object has been deleted' on the > second line, with low

Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-28 Thread Andrew Suffield
On Sat, Apr 28, 2012 at 01:05:37PM +0200, Erik Janssens wrote: > which version of PyQt are you using ? > > When in older versions (I think something like 2 releases ago), > the garbage collection kicks in in a thread and it deletes > a QObject from another thread, this object was deleted > immedia

Re: [PyQt] Disturbing evidence of garbage collection error

2012-04-28 Thread Erik Janssens
which version of PyQt are you using ? When in older versions (I think something like 2 releases ago), the garbage collection kicks in in a thread and it deletes a QObject from another thread, this object was deleted immediately, while in recent versions those are deleted later on in the event loo

[PyQt] Disturbing evidence of garbage collection error

2012-04-27 Thread Andrew Suffield
query = QtSql.QSqlQuery() if not query.prepare('select %s from %s where %s' % (','.join(field_names), table, self.key_expr(table))): I get 'RuntimeError: underlying C/C++ object has been deleted' on the second line, with low probability. Sometimes it just segfaults instead while i