Crash when run some plugins have statement "pluginType"
I have window 7 ultimate 32 bit and MuseScore 2.0.1
I see that the plugins have statement "pluginType",
they're always crash when I start them.
Ex: view.qml, scorelist.qml, helloqml.qml, random2.qml
Window notify:
The plugins is such as random.qml, notenames.qml, createscore.qml what are OK.
Is there anybody that has this problem?
Comments
Can you post a specific score you are having problems with and precise step-by-step isntructions to reproduce the problem?
In reply to Can you post a specific score by Marc Sabatella
I can say that it occurs on every scores for me, even for a simple score:
- create a new score
- enter some notes
- run plugin (ex: view.qml)
==> result is the above notification that is appear
In reply to I can say that it occurs on by travelalphaplus
Works fine for me. You enabled them in the Plugin Manager first, then ran them from the Plugins menu?
In reply to Works fine for me. You by Marc Sabatella
Yes, right, Marc.
I can't reproduce, Windows 7 Enterprise 64bit.
I try to run on some my friend's PC. It work.
Maybe, my PC don't support what MuseScore need to run these plugins.
Thanks all for replying.
In reply to I try to run on some my by travelalphaplus
Could it be the difference between 32bit and 64bit Windows?
In reply to Could it be the difference by Jojo-Schmitz
The both is good, Jojo.
In reply to I try to run on some my by travelalphaplus
double post
After trying follow guide of development page, I ran debug and saw that debugger pointed to ig4icd32.dll
Next, I searched on internet. The problem seem to relate to OpenGL, I'm not sure too.
If yes, what features of OpenGL does MuseScore need to run plugin?
In reply to After trying follow guide of by travelalphaplus
Do you have a full stack trace?
In reply to Do you have a full stack by Jojo-Schmitz
I have just known about Qt, maybe this is what you need
0 ig4icd32!DllMain C:\Windows\system32\ig4icd32.dll 0x221e95ed
1 ?? 0x1ce428bc
I have attachment file of my screen below.
Waiting.......
In reply to I have just known about Qt, by travelalphaplus
Not a useful stack trace, unfortunately ...
In reply to Not a useful stack trace, by Jojo-Schmitz
More info: After I start debug, join to MuseScore, and run plugin, to appear immediately notification below
//------------------------------------------------------------------------------------------------------------------
The inferior stopped because it received a signal from the Operating System.
Signal name : SIGSEGV
Signal meaning : Segmentation fault
//------------------------------------------------------------------------------------------------------------------
In reply to More info: After I start by travelalphaplus
Unfortunately a SIGSEGV is way to generic an error to be useful
In reply to More info: After I start by travelalphaplus
You could try to check which version of OpenGL you are running.
(For example via OpenGL Extensions Viewer http://www.realtech-vr.com/glview/download.php )
QtQuick 2, which is the framework used by the plugin engine, depends on OpenGL 2.0.
See for example here:
https://bugreports.qt.io/browse/QTBUG-27307
http://forum.qt.io/topic/19600/don-t-work-examples-on-qt-5
In reply to You could try to check which by ABL
Oh, It seem I will must have a graphic card support full OpenGL 2.0
My GPU is 100% OpenGL 1.4, 66% - 1.5 and 10% - 2.0
Thank you for your info.
In reply to Oh, It seem I will must have by travelalphaplus
Maybe this needs to get added to the prerequisites on the download page?
In reply to Maybe this needs to get added by Jojo-Schmitz
Maybe have a MuseScore build for GPU support less OpenGL 2.0 ?
In reply to Maybe have a MuseScore build by travelalphaplus
It is Qt that needs it (and MuseScore needs Qt), so no way out.
Exactly the same thing for me also with Windows 7 Ultimate 32 bits and MuseScore 2.0.1
I haven't tried on windows, but I was running into same problem on CentOS 6.7 (see issue #101171: Crash when execute plugins that bring up window in Linux AppImage (i686 & x86-64, including CentOS 6.7)). If you notice console output along the lines of:
then you might be able to resolve this issue as I did by making sure the qt5 library libqxcb-egl-integration or libqxcb-glx-integration are in the library load path.