Comment 11 for bug 1640542

As I was returning from an overlay window navigation on Twitter to an OMBUbuntu page, the webapp crashed :

Program received signal SIGSEGV, Segmentation fault.
0xabfffc56 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
(gdb) bt
#0 0xabfffc56 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#1 0xabfffeb6 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#2 0xac000128 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#3 0xaa307018 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#4 0xaa1a2a8a in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#5 0xaa27adb6 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#6 0xabbc39f6 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#7 0xab5ab4f6 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#8 0xab5be5d2 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#9 0xab5be834 in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#10 0xab5bec5e in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#11 0xa9f2107e in ?? () from /usr/lib/arm-linux-gnueabihf/libOxideQtCore.so.0
#12 0xb6dd9a2a in QObject::event(QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#13 0xb62c9ef4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#14 0xb62cdde4 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/arm-linux-gnueabihf/libQt5Widgets.so.5
#15 0x01426130 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

This was using 1.17.9

So I think the bug has been there for a while. It is just easier to trigger in 1.18, not so much in 1.17 (it took me ~10 mins. of browsing in the Twitter webapp), and even less so in 1.16