Hmmm.... Question to the Qt core experts: Is it possible that setValue(), by calling processEvents(), executes a deferred delete event on himself?
Thanks, Etienne 2014/1/23 Björn Piltz <bjornpi...@gmail.com> > I encountered a similar problem with similar code. My problem was the > following unexpected feature of QProgressDialog::setValue(): > > > Warning: If the progress dialog is modal (see > > QProgressDialog::QProgressDialog()), > setValue() callsQApplication::processEvents(), so take care that this > does not cause undesirable re-entrancy in your code. For example, don't use > a QProgressDialog inside a paintEvent()! > > In my case this lead to a stack overflow because setValue() was called > recursively. This might be your problem as well. > > > > 2014/1/23 Etienne Sandré-Chardonnal <etienne.san...@m4x.org> > >> Nope, as I'm under windows now. But I will undust my valgrind dedicated >> linux virtualbox for this... Hoping that the bug happens under linux, which >> is far from sure. >> >> I managed to trigger it with a timer and no user interaction, but it >> takes more time to crash. >> >> Cheers >> >> >> 2014/1/23 william.croc...@analog.com <william.croc...@analog.com> >> >>> On 01/23/2014 08:05 AM, Etienne Sandré-Chardonnal wrote: >>> >>> >>> Have you tried running under Valgrind >>> to see if it has anything to say. >>> >> >> _______________________________________________ >> Interest mailing list >> Interest@qt-project.org >> http://lists.qt-project.org/mailman/listinfo/interest >> >> > > _______________________________________________ > Interest mailing list > Interest@qt-project.org > http://lists.qt-project.org/mailman/listinfo/interest > >
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
