-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Segfault when connecting from an android moonlight client on Arch Linux when compiled with avx512 support #2543
Comments
What's the reason you're adding those flags? And... what are you expecting us to do? If the problem is in nanors, maybe you should file an issue, or PR, here: https://github.com/sleepybishop/nanors |
Can you provide the GDB output with the crashing stack? (and preferably also the crashing instruction) |
|
|
Crash also requires encryption to be enabled, doesn't occur when LAN encryption is forcibly disabled. |
Sunshine config Crashes if encryption is enabled Since we are using tailscale, its probably okay to disable LizardByte/Sunshine#2543 (comment) For session searching, only look at active "user" sessions
I ran into this when testing #2828 on a CPU with AVX-512 support. It was indeed a nanors bug as I suspected. The degree of memory corruption depends on the block size used, so that's why the behavior differs with and without video encryption (which adds a small header to each packet, changing the size). Once my PR is merged upstream, I'll update our nanors submodule and we can close this issue. |
Is there an existing issue for this?
Is your issue described in the documentation?
Is your issue present in the nightly release?
Describe the Bug
When connecting from an android moonlight client over LAN, sunshine segfaults before any video output can occur if it is compiled with avx512f support. The same does not occur if joining from another (linux) desktop moonlight client, or if moonlight is compiled without avx512f support.
STR:
Expected Behavior
Moonlight should connect normally, and the application should be displayed.
Additional Context
Looking at the backtrace of the coredump in GDB suggests the problem is in nanors. However, setting the forward error correction percentage to 0 doesn't solve the problem.
Host Operating System
Linux
Operating System Version
Arch Linux
Architecture
64 bit
Sunshine commit or version
373390e
Package
Linux - AUR (Third Party)
GPU Type
Intel
GPU Model
Intel Tigerlake (Gen12)
GPU Driver/Mesa Version
24.0.7
Capture Method (Linux Only)
wlroots
Config
Apps
No response
Relevant log output
The text was updated successfully, but these errors were encountered: