Hang on start if ROM path is provided as an argument with OpenGL display on Linux

[griffi-gh]

Steps to reproduce

• Start melonDS
• In "Video settings":
  • Option 1
  • Set "3D Renderer" to "Software"
  • Enable "OpenGL display" (and "VSync")
  • Option 2
  • Set "3D Renderer" to any of: "OpenGL (Classic)" OR "OpenGL (Compute Shader)"

After the emulator is set up in that way:

• Launch it normally and then load a ROM file with e.g. Drag-and-drop
  • Game launches normally
• Launch it passing the game ROM file as as argument:

  melonDS ./999.nds

  • Emulator hangs before the window appears right after outputting this in the console:

    Game is now booting
    Failed to open "./999.mch" with FileMode 0x11 (effective mode "r")
    Opened "/home/user/.config/melonDS/melonDS.toml" with FileMode 0x1 (effective mode "rb")
    Opened "/home/user/.config/melonDS/melonDS.toml" with FileMode 0x20 (effective mode "ab")

Platform

melonDS (stable 0.9.5) Linux NixOS (nixos-unstable) Wayland (qt6)

[Arisotura]

I could not reproduce. Any more details?

[Scall]

The issue is always reproducible for me on Gentoo Linux amd64 with melonDS 1.0 built from the latest code (commit 730b488), and I can work around it by passing a non-existing ROM filename as a second argument, like this:

melonDS game.nds nonexistingrom

I then click “OK” in the window saying “This ROM file does not exist” and the game starts normally.

Note:

• Passing a real GBA ROM file does NOT allow to work around the issue.
• I can also work around it by passing a ZIP archive containing an unsupported ROM, instead of the non-existing filename.
• The workaround does NOT work if the second argument is an existing empty file or another kind of file.

[Scall]

The issue can also be worked around by postponing the firmware boot through the -b/--boot option:

melonDS --boot never game.nds

and then clicking on “File” → “Boot firmware” (the title passed as an argument from the command line can be launched without issues from the firmware menu).