Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • RetroGTK RetroGTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GNOMEGNOME
  • RetroGTKRetroGTK
  • Issues
  • #6
Closed
Open
Issue created Nov 25, 2017 by Adrien Plazas@aplazasMaintainer

Run cores into a subprocess

Libretro cores should be run into a subprocess, this would ultimately allow to:

  • simplify identifying the calling-back core, hence
  • support cores calling back from a worker thread,
  • make retro-gtk more resilient to crashes in the Libretro core,
  • optionally use libseccomp to mitigate attacks coming from malicious cores or malicious games.

To do so, I propose to split RetroCore into a stub living in the user's process and a skeleton living in a worker process.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking