mirror of
https://github.com/SabreTools/MPF.git
synced 2026-02-07 13:52:12 +00:00
[Problem] MPF Crash with AOE III #706
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @eingrossfilou on GitHub (May 2, 2024).
Originally assigned to: @mnadareski on GitHub.
Before You Submit
-> No artifact newer than the stable version available
Maybe (there is a typo in the template -> hhttps)
Version
What version are you using?
Build
What runtime version are you using?
Describe the issue
MPF unexpectedly quit when search for protection in disc file.
I observe in the past that this step copies the scanned file in MPF directory. Maybe there is a collision between a file on CD and files in MPF directory. Even if it is not the case, I think it is a bad practice.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Finish protection scanning and ask for disc information
Screenshots
It just quit
Additional context
Nothing really informative in event manager apart log the crash dotnet crash
Maybe not related, but older version of MPF that were working few weeks ago crash at startup.
Event manager indicates an exception with OpenClipboard:
Look like an update of dotnet breaks some things
@mnadareski commented on GitHub (May 8, 2024):
Unrelated.
@mnadareski commented on GitHub (May 8, 2024):
Both of you should try the latest WIP here: https://github.com/SabreTools/MPF/releases/tag/rolling. Not every file will get a perfect scan since some executables are obfuscated, but it should not crash the entire dump.
@CookiePLMonster commented on GitHub (May 8, 2024):
I posted the test results of the latest rolling BOS release on Discord, as it was requested there.
@mnadareski commented on GitHub (May 8, 2024):
It appears as though it's a standard obfuscated file, especially with the presence of the repeated "expected X got Y" messages. Those usually indicate data that has been deliberately messed with. I'm glad it did not crash. This particular issue is not unique to recent versions of BOS as every executable/library, obfuscated or not, is treated the same and has been for a long time.
More samples of these obfuscated executables are needed to try to avoid the glut of messages, but that particular part of the issue is not likely to change for a while.
@mnadareski commented on GitHub (May 8, 2024):
The original issue of crashing does appear to have been fixed, though. That was an unfortunate issue stemming from libraries down the chain, not even BOS itself. If there are any more issues with crashing with the latest MPF build as linked in an above comment, then please report as such.
@mnadareski commented on GitHub (May 10, 2024):
Can either of you confirm if this issue is still happening? I believe that this has been accounted for with the various sets of fixes that have gone into the last release.
@eingrossfilou commented on GitHub (May 10, 2024):
Copy protection scan complete (and dump) ends successfully bu using
MPF_net8.0-windows_win-x64_debug.zipbuilt from commitb4d47aea37with AOE III CD1