# \[560.35.03\] GTK4 apps background CPU usage with Vulkan renderer

**URL:** <https://forums.developer.nvidia.com/t/560-35-03-gtk4-apps-background-cpu-usage-with-vulkan-renderer/311721>\
**Category:** Linux\
**Tags:** nvbugs, linux-driver, vulkan\
**Created:** [October 30, 2024, 2:31pm UTC](https://forums.developer.nvidia.com/t/560-35-03-gtk4-apps-background-cpu-usage-with-vulkan-renderer/311721 "2024-10-30T14:31:57Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![Tekstryder](https://sea2.discourse-cdn.com/nvidia/user_avatar/forums.developer.nvidia.com/tekstryder/32/393374_2.png) [@Tekstryder](https://forums.developer.nvidia.com/u/Tekstryder)\
**Post date:** [May 20, 2025, 8:59pm UTC](https://forums.developer.nvidia.com/t/560-35-03-gtk4-apps-background-cpu-usage-with-vulkan-renderer/311721/26 "2025-05-20T20:59:32Z")

</div>

> [@aplattner](#):
>
> internal bug number 5236115 for the `/proc/stat` case and 5238502 for the `futex` one

Quick strace after updating to the `570.153.02 Production Branch` driver.

Looks like the `/proc/stat` issue #5238502 may have been addressed?

```auto
[pid 5391] futex(0x7a3318000f50, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1747773368, tv_nsec=904899000}, FUTEX_BITSET_MATCH_ANY <unfinished ...>
[pid 5396] <... futex resumed>) = -1 ETIMEDOUT (Connection timed out)
[pid 5396] futex(0x5c62a658a220, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 5396] futex(0x7a330c000f50, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1747773368, tv_nsec=815262000}, FUTEX_BITSET_MATCH_ANY <unfinished ...>
[pid 5411] <... futex resumed>) = -1 ETIMEDOUT (Connection timed out)
[pid 5411] futex(0x5c62a7337400, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 5411] futex(0x7a32cc000f50, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1747773368, tv_nsec=824794000}, FUTEX_BITSET_MATCH_ANY <unfinished ...>
[pid 5396] <... futex resumed>) = -1 ETIMEDOUT (Connection timed out)
[pid 5396] futex(0x5c62a658a220, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 5396] futex(0x7a330c000f50, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, {tv_sec=1747773368, tv_nsec=825372000}, FUTEX_BITSET_MATCH_ANY <unfinished ...>
[pid 5411] <... futex resumed>) = -1 ETIMEDOUT (Connection timed out)
[pid 5411] futex(0x5c62a7337400, FUTEX_WAKE_PRIVATE, 1) = 0

```

Futexes still spinning, but CPU time consumed is improved slightly.

I’ll analyze and report accurate measurements over a longer time period.

- kernel 6.14.8
- gnome-shell 48.1 (Wayland)
- mutter 48.2 (_-Dxwayland=false -Dx11=false_)
- gtk4 4.18.5 (_-Dx11-backend=false_)
- nvidia 570.153.02

**EDIT:** Fresh boot with 6.14.8 kernel and after 6hrs uptime the CPU usage is very similar to that described in comment [#23](https://forums.developer.nvidia.com/t/560-35-03-gtk4-apps-background-cpu-usage-with-vulkan-renderer/311721/23).

So, not a statistically significant improvement, but after checking the `strace` of several GTK4+Vulkan apps, the `openat.../proc/stat` calls seem to be no longer occurring.

---

_[View the full topic](https://forums.developer.nvidia.com/t/560-35-03-gtk4-apps-background-cpu-usage-with-vulkan-renderer/311721)._