[Problem] Freezing & Opening Submission Info window before finished scanning #402

New Issue

claunia · 2026-01-29T16:15:50Z

claunia commented

2026-01-29 16:15:50 +00:00

Originally created by @PurpleNekoNova on GitHub (Feb 9, 2022).

Originally assigned to: @mnadareski on GitHub.

Version

Stable release (2.3)

Build

.NET Framework 4.8 running on (Operating System)

Describe the issue
Frozen Disc Information window while scanning. You can see the scanning numbers change in the two images while the Disc Info window is open. The Disc Info window is unresponsive and MPF freezes entirely after. Disabling archive scanning prevents this from happening.

Screenshots
https://media.discordapp.net/attachments/461797735427735562/940795918209392660/unknown.png
https://media.discordapp.net/attachments/461797735427735562/940795982277398578/unknown.png

Additional context
May be related to Blizzard's MPQ archives and how BOS handles it.

Originally created by @PurpleNekoNova on GitHub (Feb 9, 2022). Originally assigned to: @mnadareski on GitHub. **Version** - [x] Stable release (2.3) **Build** - [X] .NET Framework 4.8 running on (Operating System) **Describe the issue** Frozen Disc Information window while scanning. You can see the scanning numbers change in the two images while the Disc Info window is open. The Disc Info window is unresponsive and MPF freezes entirely after. Disabling archive scanning prevents this from happening. **Screenshots** https://media.discordapp.net/attachments/461797735427735562/940795918209392660/unknown.png https://media.discordapp.net/attachments/461797735427735562/940795982277398578/unknown.png **Additional context** May be related to Blizzard's MPQ archives and how BOS handles it.

claunia added the bug label 2026-01-29 16:15:50 +00:00

claunia closed this issue

2026-01-29 16:15:50 +00:00

claunia commented

2026-01-29 16:15:51 +00:00

@mnadareski commented on GitHub (Feb 12, 2022):

Current theory:

Crash was unrelated and likely a one-off fluke due to other things going on
Scan actually did complete before the window popped up, but the internal queue was still flushing to the log with the results of the protection scan.

If these are correct, then this is thankfully not a race condition, just a point against the internal queueing structure that MPF uses to ensure the log is consistent.

@mnadareski commented on GitHub (Feb 12, 2022): Current theory: - Crash was unrelated and likely a one-off fluke due to other things going on - Scan actually _did_ complete before the window popped up, but the internal queue was still flushing to the log with the results of the protection scan. If these are correct, then this is thankfully not a race condition, just a point against the internal queueing structure that MPF uses to ensure the log is consistent.

claunia commented

2026-01-29 16:15:51 +00:00

@mnadareski commented on GitHub (Feb 16, 2022):

I finally ran into this myself and it was what I expected. The internal queues get overloaded and need to flush. The reason I didn't notice before is that I kept the ejection reminder enabled locally, which basically allows for the queue to catch up before the info screen is shown. I will be closing this since it's not a bug, rather an unintended side-effect of a poorly-designed queueing system.

@mnadareski commented on GitHub (Feb 16, 2022): I finally ran into this myself and it was what I expected. The internal queues get overloaded and need to flush. The reason I didn't notice before is that I kept the ejection reminder enabled locally, which basically allows for the queue to catch up before the info screen is shown. I will be closing this since it's not a bug, rather an unintended side-effect of a poorly-designed queueing system.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: SabreTools/MPF#402