libretro / libretro/libretro-uae
[Switch] possible memory leak leading to crashes
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 169
- Forks
- 76
- Avg merge
- 5h 34m
- Merged PRs (30d)
- 7
Description
I'm on RetroArch 1.9.0 on Nintendo Switch with newest core available from Core Updater (PUAE 2.6.1 e187a61). Additionally, I have observed the same behavior in an older build (bundled within RetroArch 1.9.0 for Switch).
To trigger a crash it is enough to just 'Load Core -> Commodore Amiga (P-UAE)', 'Start Core', (wait a few seconds and then enter a RetroArch menu), 'Close Content', 'Load Core -> Commodore Amiga (P-UAE)' (which is NOT the same as 'Start Core') and then it crashes with 'The software was closed because an error occured'. Tried with different cores, games, even quitting and re-launching RetroArch or different homebrew. Tried with fresh config for P-UAE, all sysmodules disabled, etc. and still no deal.
So this looks like some memory leak inside P-UAE.
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
Start by reproducing the Load Core, Start Core, menu, Close Content, and second Load Core sequence on Nintendo Switch with P-UAE 2.6.1. Inspect the P-UAE core lifecycle around loading and closing content for allocations that persist across reloads; done means the sequence no longer crashes and the suspected leak is resolved.
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
- Needs clarification
- Newbie friendliness
- 25/100