libretro / libretro/RetroArch

Extremely slow to load on first startup (Windows 11), fine after (EDIT: seems to be MIDI device enumeration related)

Open
#19,247 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
14.1k
Forks
2.2k
Avg merge
7h 35m
Merged PRs (30d)
51

Description

Is there an existing issue for this?
  • This is a bug in RetroArch frontend
  • I have searched the existing issues
Description

Hi! I've noticed the last few weeks that when starting RetroArch from a fresh boot on my Windows PC, it takes a really long time to load/start, upwards of 10 - 12 seconds. If i exit the program and start it again, it starts instantly as expected.

This happens on all my computers of varying specs, from older i5-4670 to 13900. I usually keep up to date on nightlies, so I don't know the exact time this started happening, but I figure it would be very noticeable for everyone unless it's only a problem on my end.

Expected behavior

No response

Steps to reproduce the bug

Fresh boot, Windows 11 (only version I have tested on)

Launch the retroarch.exe, see how it takes a long time to open.

Exit the program, relaunch it, now it opens faster.

Version/Commit

1.22.2 1a4e631

Bisect Results

No response

Present in the nightly version

Yes, this is reproduced in the nightly build

Platform & operating system

Windows 11

Affected Cores

No response

Environment information

No response

Relevant log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Begin by reproducing the delay with retroarch.exe after a fresh Windows 11 boot, then compare it with a second launch and the nightly build. Investigate the reported MIDI device enumeration connection; done means identifying and fixing the startup delay without regressing normal launch behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop-dev, performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.