leonidx86

Reporting my test on two different Intel iGPUs, maybe this will help to locate the issue. For both tests the Linux distro and package versions are the same: - Kernel:...

> Might worth a try with mesa-git package to see if it's fixed upstream. Tested now, same result with mesa-git (version 22.0.0_devel.149533.24fef8f33da.d41d8cd98f00b204e9800998ecf8427e-1).

As an anecdotal evidence, I've tested this on several different Intel CPUs with integrated graphics. Only one of them (UHD 630) has this visual artifact (but works fine without Gamescope)....

@Oschowa You're right! With `INTEL_DEBUG=norbc` it works fine. However, with latest Mesa (22.1.0) and relatively latest Gamescope (3.11.0beta6-1) the issue is still there on UHD 630.

@Samsagax Nope. Even installed the Zen Kernel. The only major difference with your config seems to be the GPU. - GPU Intel(R) UHD Graphics 630 (CFL GT2) - linux 5.16.16-arch1-1...

The sysctl setting is also unrelated as far as I know. `echo "dev.i915.perf_stream_paranoid = 0" > /etc/sysctl.d/60-mdapi.conf` and reboot. More info: [https://www.intel.com/content/www/us/en/develop/documentation/vtune-help/top/installation/set-up-system-for-gpu-analysis.html](https://www.intel.com/content/www/us/en/develop/documentation/vtune-help/top/installation/set-up-system-for-gpu-analysis.html)

I'm getting the same error on version 6.5.0 with logs from [Keycloak](https://www.keycloak.org/) (right on start). What's interesting is that it happens randomly. Sometimes it crashes, sometimes it's not. On other...

I get similar result with a little more info (`#6`, `#7`, `#8`). ``` Core was generated by `multitail -l ./keycloak/bin/kc.sh start-dev'. Program terminated with signal SIGABRT, Aborted. #0 __pthread_kill_implementation (threadid=,...

Removed `assert`, and as you've said I see negative VMsize value. In case of Keycloak it's random. Sometimes it settles on positive value, like `2GB (VMsize)`, and sometimes negative, like...