Debug output shown in a release build after crashreporter merge
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S4 - Minor
Reproducibility
Always
Status
by design
Regression
No
Workaround
No
Project
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.1.0.5724, revision: 6f952b4
1) Load a current nightly build
Result: when loading (and exiting), I received this window and message: "Init midi driver failed etc."
-
This nightly opens fine, immediatly, as usual : 36843a3
- Not the next one (yesterday, November 25): 2023b0f
What it means? The origin?
Comments
Do you have a MIDI devices connected? If not that message is normal
No MIDI device connected.
Normal? Why?! It's unexpected, ugly and slowdown the opening/exiting.
I believe it has been that way ever since
"it has been that way ever since"
Don't understand this sentence, what you mean, and as said, the origin is this commit: https://github.com/musescore/musescore/commit/2023b0f
@cadiz1 it is normal startup behaviour to look for a MIDI device and initialise it if one is found. If none is found, the program just tells you it couldn't so that you know that the function trying to find and initialise the device worked normally. I don't know why it gives the output in a nightly, though. I thought it should be disabled for a release build (or not have a console window to send the debug messages to).
"I don't know why it gives the output in a nightly, though."
That's simply my question, and for why I opened an issue.
" I thought it should be disabled for a release build"
I hope and it's obviously the expected result.
I see output relating to crashreporter. That is a new third party library that was included yesterday. Maybe that caused a console window to be created and thus you see the other debug messages too.
And by design. It searches for a MIDI device on startup.
3.1.0.5724, is not a release build, but a development build
In reply to 3.1.0.5724, is not a release… by Jojo-Schmitz
Yes, sorry, I mean a release build configuration, as opposed to relwithdebinfo and debug. AFAIK the nightlies are built using release config?
I think they are relwithdebinfo , but I'm not 100% sure