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

[RSX Capture] Unhandled exc in rsx_thread #8259

Closed
sampletext32 opened this issue May 18, 2020 · 5 comments
Closed

[RSX Capture] Unhandled exc in rsx_thread #8259

sampletext32 opened this issue May 18, 2020 · 5 comments
Labels

Comments

@sampletext32
Copy link
Contributor

I've faced an unhandled segfault trying to open a RSX Capture from #8258.
How it happened.
I've updated RPCS3, but since I don't run games, my rig is not set up for it, so my default renderer was OGL, I've opened .rrc file from another location, not rpcs3 folder. I've found the FPS to be way less than appropriate, so decided to close a window and switch to Vulkan. But when I hit cross button, a segfault happened.

Here is the log.
RPCS3.log

Here is the capture
Mass.Effect.red.issue.RSX.capture.zip

Here is what I've seen
2020-05-18_18-26-36

My PC Specs:
Core I5 10210U
Nvidia MX250 with 2Gb VRAM.
8Gb 2667 Mhz.
1080P display 100% scale.

@sampletext32
Copy link
Contributor Author

sampletext32 commented May 18, 2020

Well another try but with Vulkan, the same segfault.
image
RPCS3.log

@kd-11 kd-11 added the Bug label May 24, 2020
@Megamouse
Copy link
Contributor

I got one trying to open this one:
BLUS30463_20200607014032_capture.zip

image

@sampletext32
Copy link
Contributor Author

RPCS3.log
Still able to reproduce on RPCS3 v0.0.12-10891-6540393d

How to reproduce.

  • Open clean RPCS3 build.
  • Ensure renderer is OpenGL
  • Run a capture from this issue
  • Close render window [you are normally about to see a "stopping emulator took too long"]
  • ReLaunch RPCS3 again
  • Set renderer to Vulkan
  • Launch the same .rrc file
  • Crash is here
    if not - retry from the very begining(just clear all caches) and after launching second time try closing the window quickly.

@Megamouse
Copy link
Contributor

Some of the bugs here seem outdated and cannot be reproduced

@Megamouse
Copy link
Contributor

A lot of changes have been made to the stop/relaunch process.
Closing to make way for more up-to-date issues.

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

Successfully merging a pull request may close this issue.

3 participants