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