Le 05/01/2019 à 20:46, Patrick Dupre a écrit :
Hello,
Was the information that I provided useful?
I also have to face other crash issues. I will try to communicate after
the previous one have been solved.
Dear Patrick,
I just stumbled on your posts while looking at my old inbox content
before leaving in vacation... I am very sorry that we did not follow up
on this.
Do you still experience this painful situation?
What I see from the log is that :
1/ the spellchecker is launched (#53-#56)
2/ it sets selection and triggers explicitly an update (#52-#53)
3/ this eventually triggers the computation of metrics for a graphics
4/ the graphics is loaded (so presumably it was not yet the case)
5/ this in turn causes a call to an external unzip program (#41-#40)
6/ the mechanism to show progress (wheel and timing) triggers (#32-#30)
7/ it updates the statusbar [#30-#26)
8/ this leads to a repaint of something (#25)
9/ the backing store (the thing on which we actually paint) of some
widget tries to synchronize itself (#16-#14)
10/ it leads to a full repaint of our workarea (why, I am not sure) (#4]
11/ this eventually crashes, presumably because the backing store is not
ready yet to receive things to paint. (#11-#10)
After wrtigin all this, that does not really help yet (except that we
could probably avoid 2/ and maybe forbid updates around 7/).
But now I notice that the warnings show first:
QBackingStore::endPaint() called with active painter on backingstore
paint device
are bugs in particular Qt versions. See e.g.
https://bugreports.qt.io/browse/QTBUG-66452
althoug this doe snot involve a crash.
So, first question: what is your Qt version?
JMarc
