Skip to content

Conversation

@nubz4lif
Copy link
Contributor

@nubz4lif nubz4lif commented Jan 2, 2026

Might've went a bit overboard with Marvel Rivals but they have several executables for some reason

Might've went a bit overboard with Marvel Rivals but they have several executables for some reason
@nubz4lif
Copy link
Contributor Author

nubz4lif commented Jan 2, 2026

Up to a maintainer as they would know better than I do, but I notice that the "GameThread" process for Marvel Rivals doesn't seem to be set correctly (nice level is 16 while the game itself is -5)

I did try adding it to the Game type and even removing the BG_CPUIO entries doesn't solve it seemingly

@Shendisx
Copy link
Contributor

Shendisx commented Jan 2, 2026

So you already tried adding the process "GameThread" to this ruleset? and it does not have any effect?

@nubz4lif
Copy link
Contributor Author

nubz4lif commented Jan 3, 2026

Ah, I checked again and it seems the crash report handler will also name itself as GameThread, so I got confused. Sorry!

Notably Marvel_Win64_Shipping will also sometimes not be named GameThread within KDEs System Monitor for whatever reason, despite it still being named that within btop

@vnepogodin
Copy link
Member

Ah, I checked again and it seems the crash report handler will also name itself as GameThread, so I got confused. Sorry!

Notably Marvel_Win64_Shipping will also sometimes not be named GameThread within KDEs System Monitor for whatever reason, despite it still being named that within btop

can you paste(for example to https://paste.cachyos.org/) the output of proc dump?

ananicy-cpp dump proc

@nubz4lif
Copy link
Contributor Author

nubz4lif commented Jan 3, 2026

Ah, I checked again and it seems the crash report handler will also name itself as GameThread, so I got confused. Sorry!
Notably Marvel_Win64_Shipping will also sometimes not be named GameThread within KDEs System Monitor for whatever reason, despite it still being named that within btop

can you paste(for example to https://paste.cachyos.org/) the output of proc dump?

ananicy-cpp dump proc

I am 99% sure this was just me being dumb but here you go

https://paste.cachyos.org/p/fffbdf6.txt

@Shendisx
Copy link
Contributor

Shendisx commented Jan 3, 2026

Yep, only the crash report client is set with a nice value of 16, all the others -5

@vnepogodin
Copy link
Member

it's correctly set

 "cmd": "Z:\\media\\NVMESSD\\Games\\Steam\\steamapps\\common\\MarvelRivals\\MarvelGame\\Marvel\\Binaries\\Win64\\Marvel-Win64-Shipping.exe",
        "cmdline": [
            "Z:\\media\\NVMESSD\\Games\\Steam\\steamapps\\common\\MarvelRivals\\MarvelGame\\Marvel\\Binaries\\Win64\\Marvel-Win64-Shipping.exe",
            "Marvel",
            "-bylauncher",
            "-culture=en",
            "None",
            "-launcher=YYP@",
            "-channel=Steam",
            "-app_channel=x20naxx2gb@steam",
            "-G7kL2mPq"
        ],
        "comm": "GameThread",
        "latency_nice": 0,
        "nice": -5,

@nubz4lif
Copy link
Contributor Author

nubz4lif commented Jan 3, 2026

Ah, I checked again and it seems the crash report handler will also name itself as GameThread, so I got confused. Sorry!

Notably Marvel_Win64_Shipping will also sometimes not be named GameThread within KDEs System Monitor for whatever reason, despite it still being named that within btop

Yeah, I was trying to say here that both processes (game and crash handler) name themselves 'GameThread', when I originally thought it was only the game naming itself that

So I thought the crash handler was the game, and saw its niceness was 16, hence the confusion

There wasn't an issue and it was just me being stupid originally, so this PR should be fine to merge

@Shendisx Shendisx merged commit 4df0caa into CachyOS:master Jan 3, 2026
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

Successfully merging this pull request may close these issues.

3 participants