MuseScore crashes on startup

• Jul 12, 2013 - 07:27
Type
Functional
Severity
S2 - Critical
Status
closed
Project

The latest nighly build for Windows, MuseScoreNightly-2013-07-12-0708-34a4d6d, but also en earlier Qt5 one, MuseScoreNightly-2013-07-11-2107-c0c5a87, crash on Startup

"The application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more Information"

Factory reset doesn't cure this.


Comments

I cannot reproduce in my Windows 8, i.e. the Nightly build starts without problems.

Have you tried to run it after deleting MinGW and Qt directories from the PATH (if you added them for compilation)?
Have you tried to run it from command line after "set PATH=" (i.e. stripping everything from the PATH)?

As a last resort you can try to add inside the bin folder of the Nightly a file named qt.conf containing the following:
[Paths]
Prefix=C:/path/to/nightly/bin

where C:/path/to/nightly/bin is the path to the bin folder of your Nightly, see also http://musescore.org/en/node/20966 .
Hope that helps.

Ciao,
ABL

I dont have MinGW or Qt installed, I'm not runing a self build Version.
That qt.conf trick doesn't work either, nor does starting it manualy with an emtpy PATH

I managed to reproduce the crash.
The crash happens if the Qt (Qt 5.1) folder is NOT present.
This happens for both my personal build and the Nightly builds: if I rename C:\Qt to C:\Qt2 then mscore.exe (or nightly.exe) does not start and it displays
Fatal: Failed to load platform plugin "windows". Available platforms are:

the qt.conf file does not help in this case.
It seems that the folder C:\Qt\5.1.0\mingw48_32\plugins\platforms, or probably only part of its content, should be copied in the bin folder of the Nightly build to make it run.

Status (old) closed active

I have exactly that probleme with nightly build from today 1806 ......
I use Windows 7 (what else should I precise ?)

Just as I don't really know what Qt5 is, I didn't test it....?

Status (old) needs info closed

And I'm pretty sure that it factory reset doesn't fix this problem, it is an entirely different issue than the on fixed here

First test with the same nightly build on another computer
* with the bin file : crash but with message like an error when using musescore (see untitled1)
* with the special file : that works

with the las nightly build R.706762c that doesn't crash anymore.

Just have to test at home tonight ^^

Attachment Size
Untitled 1.jpg 33.32 KB

oups , I shall be more attentive....
but by the way, could we then say the futur users (when it will be done) to launch from another way.....?