libretro / libretro/parallel-n64
[Nvidia, Windows] While parallel-n64 is running, closing content or exiting the emulator makes Retroarch unresponsive and crash.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 407
- Forks
- 151
- Avg merge
- 11h 53m
- Merged PRs (30d)
- 11
Description
I'm running version 2.0-rc2 of the parallel core in Retroarch 1.9. When I'm in any game and open the in-game menu, then close content or exit retroarch, the program halts. This happens every time I do so, and has for as long as I can remember.
The error I get when it crashes is the following:
Exception code=0xc0000005 flags=0x0 at 0x0000000011C5398D. Access violation - attempting to read data at address 0x0000000007C03B10
Exception code=0xc0000005 flags=0x0 at 0x0000000011C0479F. Access violation - attempting to execute data at address 0x0000000011C0479F
I've attached my console output. My pc has an Intel(R) Core(TM) i5-9600K CPU, a Nvidia RTX 2080 gpu, and runs Windows 10 Version 10.0.19042 Build 19042.
parallelbug.txt
ParaLLEl N64 .txt
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure in RetroArch 1.9 with the parallel-n64 2.0-rc2 core on Windows using the in-game menu, then review parallelbug.txt and ParaLLEl N64.txt for the reported access violations. Trace the close-content and emulator-exit paths; done means both actions complete without the emulator becoming unresponsive or crashing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100