Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • L libretro-uae
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Libretro
  • libretro-uae
  • Issues
  • #359
Closed
Open
Issue created Dec 21, 2020 by Libretro-Admin@libretro-adminMaintainer

[Switch] possible memory leak leading to crashes

Created by: ms2048

I'm on RetroArch 1.9.0 on Nintendo Switch with newest core available from Core Updater (PUAE 2.6.1 e187a61d). 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.

Assignee
Assign to
Time tracking