On maximizing the app window, the app crash with segmentation fault.

[morevnaproject-org]

On maximizing the app window, the app crash with segmentation fault.

[steveway]

Mhh, while experimenting with this using the Linux on Windows solution of Windows 10 I can get it to crash when resizing.
Interestingly it does not crash on maximize.
Also using the sides or corners resizes without crash.
But if I use the QSizeGrip on the bottom right to resize then it crashes.
And, I think I found the line which causes this by using the -m trace option of python...
In the WaveformViewRewrite, if I uncomment the QtCore.QCoreApplication.processEvents() line at the end of the resizeEvent then this does not seem to crash anymore.
I'm not sure if anything else is broken by this.
But this also seems to fix the sporadic crashes at startup mentioned in #77

[steveway]

After some more research this seems to be related to this:
https://bugreports.qt.io/browse/QTBUG-31524
It looks like calling processevents from inside an event is not recommended.

[steveway]

Mhh, I can't reproduce this crash here on Windows 10 nor in a Ubuntu 20.04 VM.
Is this reproducible or does this only happen sometimes?
A Segmentation Fault normally happens from the underlying libraries, so in this case QT is likely the culprit.
But without being able to reproduce this I can't even begin to analyse if we can do something against it.

[dadoprom]

Is this reproducible or does this only happen sometimes?

Yes, It happens almost all the time... sometimes you can maximize once and then on demaximize there the crash happens (segmentation fault)

[steveway]

That is strange, are you sure that you are using the current commit?
I can't replicate this on my Ubuntu VM at all, it nicely maximizes and de-maximizes here.
The cause could be a multitude of things, maybe the graphics-card/driver combo is problematic or the window manager does strange things.
Here on a standard Ubuntu 20.04 I can't replicate this.

[dadoprom]

perhaps try it with KDE neon 5.19 (18.04) in VM

[steveway]

Should be fixed in this: #94