Hosting a Netplay session after a content is loaded makes RetroArch crash (1.14.0 - Win64)
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Description
RetroArch crashes back to Windows, when firing the "Start Netplay Host" button, only after a content is already loaded. If the Netplay session is hosted before loading any content, RetroArch doesn't crash.
Expected behavior
Netplay session correctly hosted and ready to accept clients.
Actual behavior
RetroArch crashes back to desktop.
Steps to reproduce the bug
- Launch RetroArch (also tried as admin)
- Loading a content (tried 2 different contents, from 2 different cores)
- Choosing the core (tested with FinalBurn Neo and Genesis Plus GX)
- Choosing "Start Netplay Host" from the Netplay menu -> Host
Bisect Results
I never had the chance to not making it crash after a content got loaded, so I do suppose it has always been like this.
Version/Commit
- RetroArch: 1.14.0, Build Date: Dec 13 2022, Git Version: e3c92b0
Environment information
- OS: Windows 10, build 19045
- Compiler: [not running any local build]
Contributor guide
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 on Windows 10 with RetroArch 1.14.0 using the reported sequence: load content, choose a core, then select Netplay > Host > Start Netplay Host. Compare this with starting the host before loading content and use the crash location or diagnostic output to trace the affected netplay path. Done means hosting succeeds after content is loaded without crashing and the regression is covered by an appropriate test or reproducible verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100