Hi Gabriele, and thanks a lot for your bug report! On Sun, Oct 07, 2018 at 12:40:23PM +0200, Gabriele Mazzotta wrote: > I have a simple Qt application that's been segfaulting ever since > libqt5quick5 has been updated to 5.11.1-6. The crash does not happen > with 5.11.1-5, so I assume the problem is caused by the unaligned > memory access fix that's been backported. > > See the following example to reproduce the problem. The crash may > happen while scrolling the page, if not as soon as page is loaded. > Not all the webpages can trigger the bug. > > I can provide more info in case the example is not enough to > reproduce the problem. The problem is very similar to bug #910317, the only difference is the site address. With "https://www.qt.io";, I get the crash when running the program directly, but it does not crash when I run it in GDB. With "http://leafletjs.com/";, it crashes in GDB. However when run outside GDB, the printed stack trace is the same, so let's assume it is the same bug. I am also able to confirm that downgrading libqt5quick5 fixes the crash. But I am not sure whether this is an effect of the patch I backported (fix_unaligned_memory_access.patch), or a side effect of the rebuild. I will try a clean rebuild without the patch to check if it works. Note that the crash does not happen with Qt 5.11.2 packages from experimental (where the mentioned patch is applied too). Let's keep both bugs open for now, until I figure out which Qt module to blame (Qt Quick or Qt WebEngine). After that I will merge them. -- Dmitry Shachnev
Attachment:
signature.asc
Description: PGP signature