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

[Bug] "Sleepy" threads don't invoke the "Terminate RPCS3 unsafely" dialogue #16131

Open
Hasster1 opened this issue Sep 26, 2024 · 2 comments
Open
Assignees
Labels

Comments

@Hasster1
Copy link
Contributor

Quick summary

When a thread gets "sleepy", the dialogue for force-stopping the emulator (#14038) doesn't appear.

Details

Continuation of #16045

Since i was a bit busy (and unlucky) at the time when that issue got closed, i couldn't manage to respond in time, thus, i'm forced to make a new issue

I was informed, that whenever emulator had any problems with stopping the emulation, a dialogue would appear (#14038), prompting to either force-stop the emulation, or wait.

But, i've never saw that dialogue (which is why i made that issue in the first place).

In any case, the problem is that whenever the thread gets "sleepy", and the emulation can't stop itself, that dialogue doesn't appear at all (i've been waiting for a couple of minutes, and nothing.)

image

Attach a log file

RPCS3 (4).log

Attach capture files for visual issues

No response

System configuration

No response

Other details

No response

@elad335 elad335 self-assigned this Sep 26, 2024
@elad335 elad335 added the Bug label Sep 26, 2024
@Hasster1
Copy link
Contributor Author

I probably should also add that when you close the game while it's compiling ppu (and probably spu) modules, the game will keep compiling the last 'batch' of modules while also saying that the thread is too sleepy.

@elad335
Copy link
Contributor

elad335 commented Oct 24, 2024

That makes sense now, will fix soon

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

No branches or pull requests

2 participants