Loading Bios: 100% freeze

[asteng88]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When loading a MAME rom (I have ensured the rom works on a 1999 MAME 32 version) it loads up to the point where it says "Loading Bios: 100%" then freezes.
Setup works ok for other ROMS like NES but not for Arcade.

Setup is Docker on a Synology NAS.

Expected Behavior

Load the Bios and run the game

Steps To Reproduce

Running the frontend from Windows 11 x64 Edge, frontend loads. Choose ARCADE, Choose game...Loads ROMS up to 100% then freezes

Environment

- OS: Synology DS1618+ with DSM 7.1.1-42962 Update 6
- How docker service was installed: Docker was installed through the Synology Package Center.
I pulled the latest version using the docker pull ghcr.io/linuxserver/emulatorjs:1.9.0-ls114 when I ssh into the NAS.

CPU architecture

x86-64

Docker creation

Used synology docker gui

Container logs

Search
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    911
User GID:    911
───────────────────────────────────────
Connection to localhost (127.0.0.1) 80 port [tcp/http] succeeded!
2024/05/08 02:13:13 failed to sufficiently increase receive buffer size (was: 208 kiB, wanted: 2048 kiB, got: 416 kiB). See https://github.com/quic-go/quic-go/wiki/UDP-Buffer-Sizes for details.
Connection to localhost (127.0.0.1) 4001 port [tcp/*] succeeded!
Connection to localhost (127.0.0.1) 3001 port [tcp/*] succeeded!
Swarm listening on /ip4/127.0.0.1/tcp/4001
Swarm listening on /ip4/127.0.0.1/udp/4001/quic-v1
Swarm listening on /ip4/127.0.0.1/udp/4001/quic-v1/webtransport/certhash/uEiCHC5t_LG7wI1I-RUj1dO9o4R9rCrpllWC1tpTywCUHWA/certhash/uEiAeHgqgeu3v3NkHWSwrUyx85hAxBC1DaTX2Mb_N7ww1Hg
Swarm listening on /ip4/172.17.0.2/tcp/4001
Swarm listening on /ip4/172.17.0.2/udp/4001/quic-v1
Swarm listening on /ip4/172.17.0.2/udp/4001/quic-v1/webtransport/certhash/uEiCHC5t_LG7wI1I-RUj1dO9o4R9rCrpllWC1tpTywCUHWA/certhash/uEiAeHgqgeu3v3NkHWSwrUyx85hAxBC1DaTX2Mb_N7ww1Hg
Swarm listening on /p2p-circuit
Swarm announcing /ip4/127.0.0.1/tcp/4001
Swarm announcing /ip4/127.0.0.1/udp/4001/quic-v1
Swarm announcing /ip4/127.0.0.1/udp/4001/quic-v1/webtransport/certhash/uEiCHC5t_LG7wI1I-RUj1dO9o4R9rCrpllWC1tpTywCUHWA/certhash/uEiAeHgqgeu3v3NkHWSwrUyx85hAxBC1DaTX2Mb_N7ww1Hg
Swarm announcing /ip4/172.17.0.2/tcp/4001
Swarm announcing /ip4/172.17.0.2/udp/4001/quic-v1
Swarm announcing /ip4/172.17.0.2/udp/4001/quic-v1/webtransport/certhash/uEiCHC5t_LG7wI1I-RUj1dO9o4R9rCrpllWC1tpTywCUHWA/certhash/uEiAeHgqgeu3v3NkHWSwrUyx85hAxBC1DaTX2Mb_N7ww1Hg
RPC API server listening on /ip4/127.0.0.1/tcp/5001
WebUI: http://127.0.0.1:5001/webui
Gateway server listening on /ip4/127.0.0.1/tcp/8080
Daemon is ready
Connection to localhost (127.0.0.1) 3000 port [tcp/*] succeeded!
[ls.io-init] done.
crond[186]: USER root pid 286 cmd run-parts /etc/periodic/15min

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

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.

[thelamer]

Delete the contents of the mame bios folder and redownload the default fileset.
The mame audio samples is the biggest file that is downloaded and I need to change the code to ensure partial files are not possible.

[seemebreakthis]

Delete the contents of the mame bios folder and redownload the default fileset. The mame audio samples is the biggest file that is downloaded and I need to change the code to ensure partial files are not possible.

Had the same problem and this worked for me.

[thelamer]

I doubled the timeout, hopefully this does not occur anymore unless people are using dial up.