Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Segfault when opening URL after renderer process crash #2290

Closed
The-Compiler opened this issue Feb 7, 2017 · 0 comments
Closed

Segfault when opening URL after renderer process crash #2290

The-Compiler opened this issue Feb 7, 2017 · 0 comments
Labels
component: QtWebEngine Issues related to the QtWebEngine backend, based on Chromium. priority: 0 - high Issues which are currently the primary focus.

Comments

@The-Compiler
Copy link
Member

This segfaults in a similar way as #2289 does:

python3 -m qutebrowser --backend webengine --temp-basedir python.org ':later 2000 open chrome://crash' ':later 3000 open qutebrowser.org'

See QTBUG-58698 and this eric change for a possible workaround.

@The-Compiler The-Compiler added priority: 0 - high Issues which are currently the primary focus. component: QtWebEngine Issues related to the QtWebEngine backend, based on Chromium. labels Feb 7, 2017
@The-Compiler The-Compiler changed the title Segfault when opening URL Segfault when opening URL after renderer process crash Feb 7, 2017
The-Compiler added a commit that referenced this issue Jun 22, 2020
Qt 5.8 support was removed in April 2018 with
69a58c9, and the last crash report I got with
Qt 5.8 was in the same month.

The workaround removed in this commit still were around, and despite of what
the version check says, they are *not* needed with Qt 5.7.

Those were workarounds for the following bugs:

- https://bugreports.qt.io/browse/QTBUG-58698
  (#2290, 1af951f)

- https://bugreports.qt.io/browse/QTBUG-58982
  (#2261, 90f472b)

See #3608
The-Compiler added a commit that referenced this issue Jun 23, 2020
After 86d7943, this now also re-adds the
workaround for QTBUG-58982 (#2290) because it is apparently still needed with
Qt 5.7...

This reverts commit 87d7dd9.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: QtWebEngine Issues related to the QtWebEngine backend, based on Chromium. priority: 0 - high Issues which are currently the primary focus.
Projects
None yet
Development

No branches or pull requests

1 participant