-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 in DownloadItem.origin()
#7854
Comments
Honestly I don't remember seeing any MacOS crash dialog, and if it did, I must have dismissed it. I can help you if you know a place where MacOS stores past crash logs. If memory serves me right, though, I was downloading the file, then I stopped using the laptop and closed it, so that's maybe why the download failed. If it's pertinent to the crash, I don't know, but I still wrote it in case it's helpful |
@The-Compiler asked me to post the coredump info of the crash here. I got a segfault today after doing "Right Click" -> "Retry" on a failed download (due to insufficient disk space); qutebrowser started not responding for a bit, and then it crashed:
|
|
Still happens on Qt 6.6.1, see Probably gonna attempt an upstream report with "just" the stack trace, and add a workaround that avoids calling |
Reported upstream: [QTBUG-119763] [REG 6.5.2?] Rare segfaults in QWebEngineDownloadItem::page() - Qt Bug Tracker And with c698091, the problematic method now only gets called when doing a download from a |
Version info:
Does the bug happen if you start with
--temp-basedir
?: unknownDescription
That is here:
qutebrowser/qutebrowser/browser/webengine/webenginedownloads.py
Lines 125 to 127 in 8c2e23d
Reports:
169273992283.3258.13604852731635742755@crashes.qutebrowser.org
and169270650979.3258.6134579206996944692@crashes.qutebrowser.org
How to reproduce
Unknown, possibly retrying a download. @theitalianweeb do you know how to reproduce it? If you can, I think you should get a macOS crash dialog? If that happens, can you show the details and copy them here (instead of sending it to Apple)?
The text was updated successfully, but these errors were encountered: