White Squares, Graphical Artifacts when Browsing Streams Directory
See original GitHub issueChecklist
- I understand that Streamlink Twitch GUI is just a launcher for Streamlink
- I have read the contribution guidelines
- I have checked the list of open and recently closed issues
- I have checked the commit log of the master branch
Streamlink Twitch GUI version
v1.12.0
Streamlink version
2.3.0
Operating system, environment and configuration details
Fedora 34 (AppImage), Xorg, Intel HD Graphics 3000
Description
When opening the Top Streams directory or a game directory, there are graphical artifacts (white squares) once it is loaded. The artifacts eventually go away as you scroll or move mouse. I can reproduce this issue about 90% of the time usually by going from my followed streams to the Top Streams directory. There are errors in the debug log when it happens. This issue seems to have been introduced in the latest version as I have tested v1.11.0 and can’t reproduce.
Debug log
failed to open /usr/lib64/dri/hybrid_drv_video.so
Not using hybrid_drv_video.so
[7987:8032:0816/120920.597800:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[7987:8032:0816/120920.597959:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[7987:8032:0816/120920.598079:ERROR:object_proxy.cc(621)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
[8012:8012:0816/120920.639706:ERROR:sandbox_linux.cc(376)] InitializeSandbox() called with multiple threads in process gpu-process.
[debug][Application]
Parameters
{
"_": [],
"tray": false,
"hide": false,
"hidden": false,
"max": false,
"maximize": false,
"maximized": false,
"min": false,
"minimize": false,
"minimized": false,
"reset-window": false,
"versioncheck": true,
"version-check": true,
"logfile": true,
"loglevel": "debug",
"l": "debug",
"launch": "",
"goto": ""
}
[8016:8021:0816/120922.771778:ERROR:cert_verify_proc_builtin.cc(559)] No net_fetcher for performing AIA chasing.
[8016:8021:0816/120923.265617:ERROR:cert_verify_proc_builtin.cc(559)] No net_fetcher for performing AIA chasing.
[8012:8012:0816/120954.693831:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120954.695440:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120954.696472:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120954.926683:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120954.927240:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120955.076192:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120955.559846:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120955.846961:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120955.889677:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120956.712704:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120956.800793:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120956.843881:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120957.032535:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120957.317760:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120957.861453:ERROR:raster_decoder.cc(2167)] [.RenderWorker-0x55f277e55c90]GL ERROR :GL_INVALID_VALUE : glCopySubTexture: Cannot clear non-combineable rects.
[8012:8012:0816/120957.877261:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/120958.207054:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/121039.307373:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/121039.573436:ERROR:raster_decoder.cc(2167)] [.RenderWorker-0x55f277e55c90]GL ERROR :GL_INVALID_VALUE : glCopySubTexture: Cannot clear non-combineable rects.
[8012:8012:0816/121039.606600:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
[8012:8012:0816/121039.741789:ERROR:shared_image_representation.cc(203)] Attempt to read from an uninitialized SharedImage
Issue Analytics
- State:
- Created 2 years ago
- Reactions:2
- Comments:10 (5 by maintainers)
Top Results From Across the Web
I'm having these white boxes while browsing with Chrome. It ...
I'm having these white boxes while browsing with Chrome. It all started with the Chrome version 100 update yesterday. : r/chrome.
Read more >Do artifacts mean your graphics card is dying? What ... - Quora
Sorry for the delay in this answer. Generally, if your graphics card is dying, you will see artifacts all the time while they...
Read more >GPU Artifacting: Common Causes & How to Fix It - Cybersided
GPU artifacting can manifest itself in a variety of ways, from weird lines in the distance, strange and out of place looking textures,...
Read more >List of Physical Visualizations and Related Artifacts
This is a chronological list of physical visualizations and related artifacts, maintained by ... Missing elements are represented with a white circle.
Read more >How to Troubleshoot Display or Video Issues on a Dell Laptop
If the issue persists on the external monitor, it may be an issue with the video card (GPU) or video settings and not...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Apologies for the late update. I’ve updated to the latest version and played around with it for a couple days now. I am no longer experiencing this issue.
--disable-gpu
is a Chromium launch parameter, not something that can be set during runtime. You’ll have to add this to your launcher. Packaged applications store launchers in/usr/share/applications
and you can copy those to~/.local/share/applications
and modify them. There you can add--disable-gpu
to theExec
field.NW.js 0.57.0 has been released yesterday with the latest Chromium 94 version: https://nwjs.io/blog/v0.57.0/
I had already tried updating to NW.js 0.56.0, but the Windows builds were broken and there hadn’t been a bugfix release for some reason. cab9e21488f3d7069dc3e2eaee18dcb3fa51c7ff
I will check 0.57.0 tomorrow when I have the time. If you want to try it for yourself, change the NW.js version string in
src/config/main.json
and build the application according to the section described in CONTRIBUTING.md.