Page MenuHomePhabricator

Diff is sometimes not rendered
Open, MediumPublic

Description

Originally posted on GitHub

This only seems to happen sometimes, if I reopen Huggle enough times, the diff will render correctly, and the errors will go away for the remainder of the launch session. It doesn't render on the majority of the launches though. I can't seem to find any correlation between when it will render, and when it won't.

I'm using Arch Linux, KDE, Wayland, Nvidia, and Huggle is built using the AUR PKGBUILD.

This error occurs once at the top:

[21172:21214:0207/130051.538341:ERROR:address_tracker_linux.cc(214)] Could not bind NETLINK socket: Address already in use (98)

This error spams the console continuously on the launches where the diff isn't rendered:

[21172:21220:0207/130051.553880:ERROR:gl_context_egl.cc(259)] eglCreateContext failed with error EGL_BAD_CONTEXT
[21172:21220:0207/130051.553890:ERROR:gpu_channel_manager.cc(753)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[21172:21220:0207/130051.553892:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context
[21172:21220:0207/130051.553895:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub
[21172:21220:0207/130051.553905:ERROR:gl_context_egl.cc(259)] eglCreateContext failed with error EGL_BAD_CONTEXT
[21172:21220:0207/130051.553907:ERROR:gpu_channel_manager.cc(753)] ContextResult::kFatalFailure: Failed to create shared context for virtualization.
[21172:21220:0207/130051.553909:ERROR:shared_image_stub.cc(470)] SharedImageStub: unable to create context
[21172:21220:0207/130051.553911:ERROR:gpu_channel.cc(449)] GpuChannel: Failed to create SharedImageStub

Here's an image of the blank diff section:

image.png (787×1 px, 8 KB)

I'm happy to provide any further information if needed.

Event Timeline

Petrb triaged this task as Medium priority.Mar 2 2024, 12:49 PM
Petrb subscribed.

Hello, sorry for the late response, I am far less active these days within the Wikimedia world than I would like to be.

Unfortunately, this will probably take some time for me to debug, it's unlikely easy to replicate given it's affecting your specific setup. This could very well be some bug in Qt as well, what Qt version are compiling Huggle with? Are you using some security framework like apparmor or selinux that might tamper with the execution?

Full log of huggle startup would help, it always contains the basic info needed for debug.

Hi @Petrb, no worries. I thought it might be pretty hard to reproduce, but didn't know if there were any debug options or anything that'd make it easier. I'm using the AUR PKGBUILD of Huggle, as linked above. That uses qt5-multimedia 5.15.12+kde+r2-1 and qt5-webengine 5.15.16-3 if that helps. I don't believe AppArmor or SELinux is interfering. I'm happy to provide a full log, should I just capture the stdout into a file and post it here?

I have come across https://github.com/jellyfin/jellyfin-media-player/issues/165 while searching for the error. Although it's a different application, it's the same error, and it seems like the same rendering issue. Using QT_QPA_PLATFORM=xcb as suggested in that issue fixes it for me here. That issue also links to https://github.com/intel/libva/pull/790, so it might just be an upstream issue. I'm not experienced enough in this area to be able to know for certain though.

Thanks for your help.