[MSVC] MuseScore failed to run 5 tests on MSVC

Issue type

Choose option...

Description with steps to reproduce

Hi All,

MuseScore failed to run 5 tests on MSVC on windows. It can be reproduced on https://github.com/musescore/MuseScore/commit/3e4778a commit on main branch. Could you please help look at this issue?

Failed tests:

The following tests FAILED:
	  8 - muse_audio_tests (SEGFAULT)
	 11 - muse_draw_tests (Failed)
	 23 - engraving_tests (Failed)
	 32 - iex_mnx_tests (Failed)
	 33 - iex_musicxml_tests (Failed)

Repro steps:

1. git clone https://github.com/musescore/MuseScore.git C:\gitP\musescore\MuseScore
2. cd C:\gitP\musescore\MuseScore
3. mkdir build && cd build_amd64
4. download "https://s3.amazonaws.com/utils.musescore.org/dependencies.7z to C:\gitP\musescore\MuseScore\dependencies
5. cd /d C:\gitP\musescore\MuseScore\build
6. pip install aqtinstall
7. python -m aqt install-qt windows desktop 6.10.2 win64_msvc2022_64 --modules qtshadertools qt5compat qtnetworkauth qtscxml --outputdir C:\Qt
8. cmake -G "Visual Studio 18 2026" -A x64 -DCMAKE_SYSTEM_VERSION=10.0.26100.0  -DBUILD_UNIT_TESTS=ON -DMUE_COMPILE_QT5_COMPAT=ON -DCMAKE_PREFIX_PATH="C:\Qt\6.10.2\msvc2022_64" ..
9. msbuild /m /p:Platform=x64 /p:Configuration=Release MuseScoreStudio.slnx /t:Rebuild
10. set PATH=C:\Program Files\Git\usr\bin;%PATH%
11. set PATH=C:\Qt\6.10.2\msvc2022_64\bin;%PATH%
12. set PATH=C:\gitP\musescore\MuseScore\dependencies\libx64;%PATH%
13. set PATH=C:\gitP\musescore\MuseScore\build\_deps\freetype\bin;%PATH%
14. set PATH=C:\gitP\musescore\MuseScore\build\_deps\harfbuzz\bin;%PATH%
15. set PATH=C:\gitP\musescore\MuseScore\build\_deps\libpng\bin;%PATH%
16. set QT_PLUGIN_PATH=C:\Qt\6.10.2\msvc2022_64\plugins
17. ctest --build-config Release --output-on-failure -V

Supporting files, videos and screenshots

Test-1.log

In which versions of MuseScore Studio is this issue present?

Main branch latest version

Regression

No.

Operating system

Windows 11

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible