Description
Selective media indexing (e.g. indexing a single system like NES) gets stuck at the "Initializing database" phase for 6+ minutes on MiSTer with no progress notifications emitted.
This was observed after cancelling a full index mid-way (partial DB with ~68k entries), then starting a selective index for ["nes"]. The status stays at Initializing database with totalSteps: 0, totalFiles: 0 indefinitely.
Expected behavior
Selective index initialization should complete in a reasonable time, even with a large existing database. Progress should be reported during initialization.
Observed on
- Platform: MiSTer (arm)
- DB size at time of test: ~68k partial entries from a cancelled full index
- Version: 0bd2937-dev
Likely cause
PopulateScanStateForSelectiveIndexing loads all existing data from the database to avoid ID conflicts. With a large number of existing entries this could be very slow on MiSTer's hardware (single SQLite connection, ARM CPU). No progress updates are emitted during this phase.
Description
Selective media indexing (e.g. indexing a single system like NES) gets stuck at the "Initializing database" phase for 6+ minutes on MiSTer with no progress notifications emitted.
This was observed after cancelling a full index mid-way (partial DB with ~68k entries), then starting a selective index for
["nes"]. The status stays atInitializing databasewithtotalSteps: 0, totalFiles: 0indefinitely.Expected behavior
Selective index initialization should complete in a reasonable time, even with a large existing database. Progress should be reported during initialization.
Observed on
Likely cause
PopulateScanStateForSelectiveIndexingloads all existing data from the database to avoid ID conflicts. With a large number of existing entries this could be very slow on MiSTer's hardware (single SQLite connection, ARM CPU). No progress updates are emitted during this phase.