That is my problem: reproduction is hard, I get no more info in monitor.log or on the command line.
I guess the monitor thread holds a "last reference" of an QtDialog object which causes the error when the thread reduces the ref count to zero and destructors in Qt are called. My current dirty workaround is to introduce a global list which keeps references to my QDialog instances, so that the monitor process has no chance to induce destruction. This is realy a dirty workaround but if this modification avoids the crushes my assumption is right. Regards, Uwe On Jan 10, 8:36 am, anatoly techtonik <[email protected]> wrote: > As for me, I don't know such bug. Non-repeatable bugs are hard to find, so > if you experience the issue repeatedly - try to dig as much info as > possible. -- You received this message because you are subscribed to the Google Groups "spyder" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/spyderlib?hl=en.
