[Interest] linux 64 5.7.0 WebEngine segfault

[Kevin Mcintyre]

Kai - The segfault was due to trying to implement
QWebEngineUrlRequestInterceptor and set
page().profile().setRequestInterceptor -- I haven't seen any working
examples...so I'm just assuming I messed something up.  Once I commented
out this assignment everything worked smoothly.



On Mon, Jun 20, 2016 at 5:50 AM, Kai Koehne <Kai.Koehne at qt.io> wrote:

> Hi Kevin
>
> > -----Ursprüngliche Nachricht-----
> > Von: Interest [mailto:interest-bounces+kai.koehne=qt.io at qt-project.org]
> > Im Auftrag von Kevin Mcintyre
> > Gesendet: Freitag, 17. Juni 2016 18:23
> > An: interest at qt-project.org
> > Betreff: [Interest] linux 64 5.7.0 WebEngine segfault
> >
> > When starting webengine - I get this error,
> >
> > [0617/091642:ERROR:browser_main_loop.cc(217)] Running without the SUID
> > sandbox! See
> > https://chromium.googlesource.com/chromium/src/+/master/docs/linux_s
> > uid_sandbox_development.md for more information on developing with the
> > sandbox on.
>
> This is actually just a warning that one can ignore. We'll silence it in
> 5.7.1.
>
> > followed by this segfault
> >
> >
> > kernel: [37309.009921] Chrome_IOThread[7824]: segfault at 61 ip
> > 00007f65a7ae2baa sp 00007f656cc18300 error 4 in
> > libQt5WebEngineCore.so.5.7.0[7f65a7486000+4e16000]
>
> Do you have a stack trace for this? Which example/page does it happen for?
>
> I'd appreciate getting a full bug report on bugreports.qt.io (Qt project,
> WebEngine component).
>
> Regards
>
> Kai
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20160620/352803db/attachment.html>