8173a48b8a
When QtWebEngine shuts down, it calls pending callbacks, which means we access an invalid 'settings' object when that happens. The stack would look something like this: 0 QtWebEngineCore::WebEngineSettings::setAttribute(QtWebEngineCore::WebEngineSettings::Attribute, bool) 12 QtWebEngineCore::CallbackDirectory::invokeEmptyInternal<QVariant const&>(QtWebEnginePrivate::QWebEngineCallbackPrivateBase<QVariant const&>*) 14 QtWebEngineCore::CallbackDirectory::~CallbackDirectory() 19 QWebEnginePage::~QWebEnginePage() If we instead get the settings from the view freshly, we get a RuntimeError from PyQt telling us that it's dead. Not sure why it doesn't know about settings being dead... With that, we'd get a RuntimeError, which we can simply ignore as it doesn't matter anyways if the tab is gone. Fixes #3399 |
||
|---|---|---|
| .. | ||
| help | ||
| img | ||
| backers.asciidoc | ||
| changelog.asciidoc | ||
| contributing.asciidoc | ||
| faq.asciidoc | ||
| install.asciidoc | ||
| quickstart.asciidoc | ||
| qutebrowser.1.asciidoc | ||
| stacktrace.asciidoc | ||
| userscripts.asciidoc | ||