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

Gamescope + Nvidia driver 570.124.04 will not open Path of Exile 2 #1759

Open
3 of 6 tasks
GloriousEggroll opened this issue Feb 28, 2025 · 5 comments
Open
3 of 6 tasks

Comments

@GloriousEggroll
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Are you using any gamescope patches or a forked version of gamescope?

  • The issue occurs on upstream gamescope without any modifications

Current Behavior

Trying to run Path of Exile 2 within gamescope, all attempts fail:

gamescope --hdr-enabled -W 3840 -H 2160 -b --mangoapp -- %command%
gamescope -W 3840 -H 2160 -b -- %command%
gamescope -b -- %command%
gamescope -- %command%

Works on previous driver version 570.86.16. Same first command works on other games (tested Avowed and Path of Exile 1)

When running steam from console, gamescope says:

[Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.
info:  Memory type mask for sparse resources: 0x2
info:  Memory type mask for buffer resources: 0x1f, usage: 0x219ff
warn:  DXVK: No state cache file found
info:  DXVK: Graphics pipeline libraries supported
[gamescope] [Error] vulkan: vkAllocateMemory failed (VkResult: -2)

Steps To Reproduce

Try running Path of Exile 2 in steam with any of these options:

gamescope --hdr-enabled -W 3840 -H 2160 -b --mangoapp -- %command%
gamescope -W 3840 -H 2160 -b -- %command%
gamescope -b -- %command%
gamescope -- %command%

Hardware information

- Distro: Nobara Linux
- CPU: 9800X3D
- GPU: Nvidia 4080 Super
- Driver Version: 570.124.04

Software information

- Desktop environment: KDE Plasma 6.3.0
- Session type: Wayland
- Gamescope version: 3.16.1
- Gamescope launch command(s): 

`gamescope --hdr-enabled -W 3840 -H 2160 -b --mangoapp -- %command%`
`gamescope -W 3840 -H 2160 -b -- %command%`
`gamescope -b -- %command%`
`gamescope -- %command%`

Which gamescope backends have the issue you are reporting?

  • Wayland (default for nested gamescope)
  • DRM (default for embedded gamescope, i.e. gamescope-session)
  • SDL
  • OpenVR

Logging, screenshots, or anything else

This is the last bit of relevant info that came through the terminal before it crashed:

info:    maintenance5                           : 1
info:  VK_KHR_present_id
info:    presentId                              : 1
info:  VK_KHR_present_wait
info:    presentWait                            : 1
info:  VK_NV_descriptor_pool_overallocation
info:    descriptorPoolOverallocation           : 1
info:  VK_NV_low_latency2
info:    extension supported                    : 1
info:  VK_NV_raw_access_chains
info:    shaderRawAccessChains                  : 1
info:  VK_NVX_binary_import
info:    extension supported                    : 1
info:  VK_NVX_image_view_handle
info:    extension supported                    : 1
info:  VK_KHR_win32_keyed_mutex
info:    extension supported                    : 1
info:  Queue families:
info:    Graphics : 0
info:    Transfer : 1
info:    Sparse   : 0
[Gamescope WSI] Forcing on VK_EXT_swapchain_maintenance1.
info:  Memory type mask for sparse resources: 0x2
info:  Memory type mask for buffer resources: 0x1f, usage: 0x219ff
warn:  DXVK: No state cache file found
info:  DXVK: Graphics pipeline libraries supported
[gamescope] [Error] vulkan: vkAllocateMemory failed (VkResult: -2)
7039.494:0124:0128:trace:seh:register_module_exception_directory count 57, max_count 512.
7039.494:0124:0128:trace:loaddll:build_module Loaded L"C:\\windows\\system32\\xinput1_4.dll" at 00006FFFFB130000: builtin
7039.643:0124:0128:fixme:gdiplus:resample_bitmap_pixel Unimplemented interpolation 7
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles
7039.647:0124:0180:err:font:alloc_font_handle out of realized font handles

I don't think the alloc_font_handle issue is relevant, game works without gamescope.

@matte-schwartz
Copy link

matte-schwartz commented Feb 28, 2025

I see this issue as well with PoE 2 on 570.124.04 with gamescope 3.16.1 on a 4090.

in my dmesg on the open modules, every time gamescope crashes I get this new kernel warning as well from NVRM:

Feb 27 19:22:25 nvidia-arch kernel: NVRM: dmaAllocMapping_GM107: Virtual address 0xACE0000 is not compatible with page size 0x200000 or page offset 0x0.
Feb 27 19:22:25 nvidia-arch kernel: gamescope-xwm[50727]: segfault at 80 ip 00005a5fdf1fe547 sp 00007e8902dfd0e0 error 4 in gamescope[a0547,5a5fdf171000+204000] likely on CPU 16 (core 32, socket 0)

nvidia-bug-report-open.log.gz

I took a look at the latest driver release notes and I wasn't really seeing anything that suspicious. @cubanismo any ideas if there was something in the release that may have to do with this kernel error?

the closed modules also crash, but without the kernel warning like the open modules:

nvidia-bug-report-closed.log.gz

@matte-schwartz
Copy link

@cubanismo
Copy link

Thanks for the report. For reference, I've filed NVIDIA internal bug 5138983 to track investigation of this issue.

I'm not currently able to deduce a cause from the info so far, but the nvidia-bug-report logs, the notes about previous driver versions working, and the kernel log error messages will be very helpful in tracking it down. Thanks for including all that info.

@abchauhan-nv
Copy link

Hi all,

I am a member of the NVIDIA QA team and can reproduce the issue on our systems. This is under investigation.

Works on previous driver version 570.86.16

Can you please help confirm if this works on 570.86.16. On our systems, we can reproduce the issue on 570.86.16 as well.

Configuration :- Arch Linux (packages up to date), RTX 3060, 570.86.16, KDE Wayland session, gamescope 3.16.1

Thanks!

@matte-schwartz
Copy link

hi @abchauhan-nv after double-checking yes, I was able to trigger the crash on 570.86.16 as well. oddly enough, it only started to happen once I toggled HDR from disabled -> enabled on my KDE Wayland session. On the latest driver, I had it go from working to not working in the same boot here:

nvidia-bug-report.log.gz

I'd also maybe recommend verifying against gamescope-git, which you can grab from the AUR. I seem to have a lot more difficulty reproducing the crash on there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants