The segefault is caused by repeated calls to start and stop the gtk
main_loop in a single python process. WebKit does not like the repeated
start and stops in main_loop, maybe because some state is left behind.
The test browser is stable called repeatedly in a subprocess. This is
slower than working the browser in proc.
** Changed in: html5-browser
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/800741
Title:
segfault in libwebkitgtk-3.0.so.0 on amd64
To manage notifications about this bug go to:
https://bugs.launchpad.net/html5-browser/+bug/800741/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
