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

Hangs with reddit url #8109

Open
jnglg opened this issue Feb 21, 2024 · 5 comments
Open

Hangs with reddit url #8109

jnglg opened this issue Feb 21, 2024 · 5 comments
Labels
status: can't reproduce Issues which can't be reproduced. status: needs triage Issues/PRs which need some deeper investigation.

Comments

@jnglg
Copy link

jnglg commented Feb 21, 2024

Hi. Thanks for this great software!

Version info:
qutebrowser v3.1.0
Git commit:
Backend: QtWebEngine 6.6.1, based on Chromium 112.0.5615.213 (from api)
Qt: 6.6.1

Does the bug happen if you start with --temp-basedir?
No. Edited on 2024-03-28: sorry yes it does.

Description
I usually keep 30-60 various tabs opened on 3 windows without issue.
Each time I tab-open a reddit url, usually from a search engine, it needs some time to half-load, then it hangs, always. The computer's fans speeds up.

Usually the tab displays a "Unable to load page" after a few seconds or minutes. Sometimes, one or two of the previous tabs end with a "Unable to load page" as well (the one with the search engine's results). I'm able to close the tabs, open the url again and maybe quickly scroll to read other answers before it crashes. In the reddit webpage, usually the mouse cursor doesn't change on hover and supposedly clickable items are not clickable.

If not lucky, the system becomes very unresponsive as soon as I try to open the url. I might get it back by 'ps -e' and killing qutebrowser (typing blindly) but it takes half an hour.

It's been like this for a few weeks or months.
It happens whenever I open a reddit url. It has never happened with another one as I know of.

It does not happen with --temp-basedir.

In the terminal:

$ qutebrowser --temp-basedir
$ libva error: vaGetDriverNames() failed with unknown libva error
[2781115:2781144:0221/144540.204137:ERROR:gpu_memory_buffer_support_x11.cc(49)] dri3 extension not supported.
libpng warning: iCCP: known incorrect sRGB profile
libpng warning: iCCP: known incorrect sRGB profile

The web page displays :
Unable to load page
Error while opening https://www.reddit.com/r/blahblahblah
Renderer process was killed (status 9)

Try again

How to reproduce

https:www.reddit.com

Not sure how.
The only thing I can reproduce with a --temp-basedir launch is that when hovering in a reddit page, the items (links, expand answers...) on the page are not clickable for some time. Thus it seems to be related to a Javascript mess, but since the web is mostly made of javascript mess nowadays...

What should I look for?

@toofar
Copy link
Member

toofar commented Feb 21, 2024

Some things to try:

  • turn javascript off and see if it starts working
  • check if you had any redirectors registered (eg www.reddit.com -> old.reddit.com) which might be having issues
  • have a look through qute://configdiff/ and see if you can spot what setting you've changed could be causing it (maybe check qt.args in particular due to the graphics error message)

@The-Compiler
Copy link
Member

@jnglg Any updates? I doubt the issue is directly related to qutebrowser.

@The-Compiler The-Compiler added status: can't reproduce Issues which can't be reproduced. status: needs triage Issues/PRs which need some deeper investigation. labels Mar 26, 2024
@jnglg
Copy link
Author

jnglg commented Mar 28, 2024

Hi Florian and all.

I gave it another try today.
It still fails and it also fails with --temp-basedir. I was wrong about that in my original post, sorry, I didn't wait enough time.

I also tried after
$ /usr/bin/rm -Ir ~/.local/share/qutebrowser/webengine/.org.chromium.Chromium.*
then after
$ /usr/bin/rm -Ir ~/.local/share/qutebrowser/webengine/*
then after
$ /usr/bin/rm -Ir ~/.cache/qutebrowser/*
and finally with qutebrowser --temp-basedir.

But it fails after a few minutes, not just after a few seconds as before doing the cleaning.

What I find interesting is which tabs fail and how.

Let's open a new window.
Let's search something with the keyboard shortcut o (for :open). It opens a duckduckgo web page with the search results. Let-s ctrl-click to open a first result (any web page which isn't in reddit) in a new tab and then a second search result, one in reddit.com, in another tab.
After a while, all three tabs get the error "Renderer process was killed".
The other existing Qutebrowser windows, with multiple tabs, are not affected.

Let's kill this window and do it again. But first, open a tab with some page or other, let it be "lemonde.fr", a french newspaper. It's javascript-heavy but as I use hostsblock (is it relevant...), a lot of the mess is probably trimmed.
Then let's create another tab and do a duckduckgo search again with the keyboard shortcut O (for :open -t), as before. We now have four tabs, the tabs #2, 3 and 4 are the same as the tabs #1, 2 and 3 respectively from the first experiment. After a while, the fourth tab with reddit gets the error, the third tab as well, the second one with the duckduckgo search gets the error, like before. But the first tab, with the whatever web page, does not get contaminated. The pandemic seems to stop at the duckduckgo page from which the reddit tab was created but it contaminated the innocent tabs created from this very search page. Please see the screenshots.
renderer_process_crashed
unaffected_tab

@The-Compiler
Copy link
Member

Sounds like you might just be running out of RAM? What does free -m say, and what does dmesg have to say after this happens?

@pylbrecht
Copy link
Collaborator

I am having the same issues when opening reddit URLs. Once I get a free minute I will drop my details in a comment and start debugging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: can't reproduce Issues which can't be reproduced. status: needs triage Issues/PRs which need some deeper investigation.
Projects
None yet
Development

No branches or pull requests

4 participants