Open mauricioquintela opened 3 months ago
The crash is unrelated and #7901.
As for the slowness, that seems like an issue with your graphic driver or something. I just upgraded and don't notice any difference, and this is almost certainly unrelated to any recent changes in qutebrowser.
Could you try running the testbrowser script and see if it reproduces with that too?
Running with the testbrowser script works perfectly. It's weird if indeed it is a graphics driver issue, as no driver update has happened for a few days, with several reboots and shutdowns in the meanwhile.
Version info:
Does the bug happen if you start with
--temp-basedir
?: YesDescription Attempting to use qutebrowser after latest commit (https://github.com/qutebrowser/qutebrowser/commit/0b220117e2c26dd3ca7639a7bda78a44c8959fbf) is essentially impossible, with the browser running at a snail's pace and (sometimes) crashing crash.txt. Latest commit was compiled after a libx11 update (see https://archlinux.org/packages/extra/x86_64/libx11/), which might be related. Logs obtained from running qutebrowser via
qutebrowser -T --debug 2>|log.txt :version
: log.txt. Libva error also appears when runningvainfo
, although I am not sure the was the case previously:How to reproduce
Try to open qutebrowser under latest commit + libx11 version. Interface should be extremely slow opening any starting page (duckduckgo, searx, google, etc). Forcing qutebrowser to start in the :version page leads to normal scrolling, although opening a new tab (to about:blank) leads to same slowdown. Search boxes or typing an url can lead to crash.