This repository was archived by the owner on Jun 9, 2025. It is now read-only.
This repository was archived by the owner on Jun 9, 2025. It is now read-only.
[BUG] retroarch hangs when exiting game #77
Not planned
Description
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
It's my first time using emulatorjs. I'm having issues when closing/exiting a game. Either pressing ESC twice, or going into the retroarch menu and quitting, the window freezes and I'm unable to get to the main menu again.
Expected Behavior
I should be able to go back to the rom selection screen again.
Steps To Reproduce
- Browse the game you want to play
- Start it
- Press ESC twice to exit.
Environment
- OS: Debian Bookworm
- How docker service was installed: via docker compose.
CPU architecture
x86-64
Docker creation
---
services:
emulatorjs:
image: lscr.io/linuxserver/emulatorjs:latest
container_name: emulatorjs
environment:
- PUID=1000
- PGID=1000
- TZ=Etc/UTC
- SUBFOLDER=/ #optional
volumes:
- /path/to/config:/config
- /path/to/data:/data
ports:
- 3000:3000
- 80:80
- 4001:4001 #optional
restart: unless-stopped
Container logs
Nothing relevant in the logs.
Metadata
Metadata
Assignees
Type
Projects
Status
Done
Milestone
Relationships
Development
No branches or pull requests
Activity
github-actions commentedon May 12, 2024
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
thelamer commentedon May 12, 2024
The method to exit a game is to press back on the browser. This catches and ensures the save data is dumped:
https://github.com/linuxserver/emulatorjs/blob/master/frontend/js/index.js#L225-L233
This can also be triggered on a controller with the xbox button three times quickly.
The only time you would need to clean exit retroarch using escape like this is if you made a series of settings changes and wanted the config to be dumped to the browsers local storage.
Basically this is known behavior.
LinuxServer-CI commentedon Jun 12, 2024
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
github-actions commentedon Sep 10, 2024
This issue is locked due to inactivity