Created attachment 161 [details]
test case

See example code.

Basically, when I return a new instance of my custom QObject subclass, it seems
to get freed when it falls out of scope, and therefore it segfaults. When I
leak a reference to the object I'm returning (i.e. as attribute to the list
model), this problem is worked around.

The object should be kept alive as long as the caller needs it, but should be
freed after that.

By default, the attached code crashes with PySide Git HEAD. If you set
"enable_leaking = True", a reference to the object is saved as attribute in the
model, thereby avoiding it being freed at return time.

(Sorry for the confusing explanation, the code should make things clear ;)