(SOLVED) V.4.1.1 still stalls and crashes
V.4.1.1 still stalls for quite a while when calling up "styles". It also still crashed on just clicking text boxes. This is not a exotic machine, it's a Surface Book3 with recent processor and decent power. I will need to go back to v3 or Sibelius, this is not usable, it kills too much time and I was patient for an eternity ... always thought, this is going to be sorted out soon.
Comments
You might check some things here: https://musescore.org/en/node/339915
For the crash, please attach your score and give precise steps to reproduce the problem.
For the style dialog delay, for some reason, the Surface line seems to have something going on that triggers this relatively unusual problem more often than other machine. We've got maybe a dozen or reports out of millions of users, and almost half are from Surface owners. Probably not a coincidence, but I don't know what it might mean. Some particular piece of hardware or device driver used across the Surface line, perhaps. See for example https://github.com/musescore/MuseScore/issues/13193. Anything you can do to help track down why this issue happens for some and not for most would be most welcome!
In reply to For the crash, please attach… by Marc Sabatella
Hi & thx for taking care.
Here is a file that crashes on just selecting the headlines, sometimes the first click, for sure the second one.
The styles windows delay occures on both my machines I use for music, one is the Surface Book3 i7-12th.gen, the other one a HUSN fanless with i3-8th.gen w/out TPM. Both run the latest 4.1.1 .paf from the same cloud folder which used to work like a charm on v3.6
Greetings
Uwe
In reply to Hi & thx for taking care… by urhs
I'm not able to reproduce any crash clicking any text in this. Can you give more precise steps?
There have been a couple of other reports of systems that crash when trying to press Enter within the title field or certain other specific operations - cases where it's reproducible on those two or three systems but no others. This might turn out to be another case of that. This problems seems more rare than the slow style dialog, but both are very uncommon and still mysterious.
In reply to I'm not able to reproduce… by Marc Sabatella
Here you are... an .mp4 showing the incident. Use Your last name as password.
https://1drv.ms/f/s!Apr3Uh4YYIvVlfZpSvL7crs7tH_3NA?e=5yvqwS
Greetings
Uwe
In reply to Here you are... by urhs
Or you can zip the file and post it here.
In reply to Here you are... by urhs
Couldn't tell, but in the first mp4 it looked like your final action was a click to close the score. Then the crash alert appeared. Not sure what to make of that but I can report that 80+% of the time MuseScore 4 crashes when I close it. But that's okay because I avoid MuseScore 4 and use it only for testing new features, mulling the UI changes, and trying VST libraries.
The lure of v4 is compelling now that I have Kontakt and PianoTeq working in MuseScore 4.1.1 ... but not enough so to make me want to endure the persistent and multifaceted playback issues, starting with the half-second delay between note-click and hearing the clicked note's pitch. MacOS 13.5. MacBook Air M2.
scorster
In reply to Couldn't tell, but it looked… by scorster
That shouldn't happen. Have you started a thread asking for help with that? Both the crash on exit and the latency after click - neither should happen. There is presumably something quite unusual going on with your particular system that other users may be able to help you work around.
In reply to That shouldn't happen. Have… by Marc Sabatella
Hi Marc,
I've posted three topics on clicked notes in MS4.
The first is about the delay that I mentioned earlier in this thread.
Here are the other posts two:
https://musescore.org/en/node/322984
https://musescore.org/en/node/314090
scorster
In reply to Hi Marc, I've posted three… by scorster
Seems like no one has yet figured out the specific combination OS settings or third-party software/hardware that are causing this issue on your system and a handful of others. Definitely keep experimenting - there must be some simple logical explanation for why some systems seem to experience this. Then if the trigger is ever identified, that would be the first step in allowing the developers to reproduce the issue and then begin to devise a solution.
Those other posts seem to predate MU4 by a couple of years; not sure what they were supposed to indicate?
In reply to Seems like no one has yet… by Marc Sabatella
I made the surface book revert/reinstall windows keeping user data but deleting/reinstalling 3rd party software. The issue disappeared, no crash now, and styles window opens within 8s. Not sure what to draw from that, though ...
In reply to I made the surface book… by urhs
Sorry you had to go to that extreme. But with computers you never know. Good luck.
In reply to Sorry you had to go to that… by bobjp
well, guess what, this test was on PAF (portable app), and...
this identical installation, synched by onedrive, works now on the reinstalled surface win11, still it does not on the win10 desktop (up to date but not reinstalled).
there must be an update issue within windows causing all this, some thing(s) that did not get updated incrementally for some reason over the past year (since I have the surface book).
so, sorry to say, people need to take a few hours to refresh their win installation and put their desktop environment back together.
still, i don't know, why styles need 8s to come up, but it is definetely better than the 30s before...
In reply to well, guess what, this test… by urhs
Styles take several seconds to come up on my system, also. But I don't use it that often.
In reply to Here you are... by urhs
I'm not able to access the video, but simply typing up the steps is far simpler to follow than any video
In reply to I'm not able to access the… by Marc Sabatella
Well, Marc, the steps are as I said before. In the one video, I click the headlines from top down, in this case it crashes after the second (can't click the third anymore), then I close the app to show that it crashed.
Excting the app doesn't make it crash here, scorser, this was only to proof visibly, it crashed.
In the other video, you see the styles window taking 30s to come up. On a 12thgen i7.
Marc not sure why you cannot access the video, I checked with a incognito window and was able to play it back within overdrive online.
Attaching didn't work yesterday, no matter what I attached, not even a.txt.
In reply to Well, Marc, the steps are as… by urhs
👋 Just solved it for now 👋
I was thinking, maybe it's a resource version issue, so I checked if MuseScore uses VisualC or stuff like that. It doesn't.
Then I thought, okay, if it is just few machines, I will try to turn off windows security measures one by one, maybe something is malconfigured here. What can I say, turning off "check apps and files" within "reputation-based protection" already did it. No crash, delay down to 3 seconds (still not great but okay). Turned it back on - still fine - so maybe, there is a thing that gets reset when you toggle that switch.
So that was for the Win11 Surface Book, I will now try to find out about the other machine (Win10 NoName).
Please fwd this info to people involved since I cannot waste more time on bug tracking (git or whatever) hubs
In reply to 👋 Just solved it for now 👋 I… by urhs
Sorry, that was not it. Issue came back.
In reply to 👋 Just solved it for now 👋 I… by urhs
Even if it came back, the fact that it seemed to make a difference at all is indeed potentially useful information.
And - helping each other out here is never a waste a time of time :-). I and others spend hours a day answer questions and helping people resolve problems, and while not everyone has that kind of time, if those who experience a rare crash unreproducible by others are able to spend a little time trying to track down the source of the problem, that helps all other users as well.
In reply to Well, Marc, the steps are as… by urhs
I don't know what a "headline" is in this context, so that is why I wanted a more precise describe of what you are doing. Writing up steps would take less time than making and posting a video and be easier to follow.
But if in addition to the written out steps you feel a video would also help clarify, simply upload to YouTube as unlisted then paste a link here.
In reply to I don't know what a … by Marc Sabatella
i'm sorry, "headlines" meant title, subtitle, composer, in that order.
I totally agree with you - it is just that I cannot get into this too much, there is lack of knowledge about programming on one side and simply another lack - time.
I don't do youtube but the above link works, just give it another try. I simply shared a onedrive folder and set "Sabatella" as password.
In reply to i'm sorry, "headlines" meant… by urhs
okay, don't look for it, i decided to clean the pc from anything "musescore", including the registry, windows security, firewall etc etc. will be back after superclean install
In reply to i'm sorry, "headlines" meant… by urhs
OK, I clicked those fileds in that order, and no crash. I also tried double-click just in case, same result. Not really surprising, as I said, based n the handful of similar reports, this seems reproducible on those systems but on none others.
As for the video:
For me when I enter that password, I then get a security error - OneDrive telling me I'm trying to access sensitive information and need to enter my own password for my own account. I shouldn't need to do that just to watch a video. If you don't want to use something that works universally like YouTube, you can try Vimeo or any of a bunch of other video hosting services. But having a plain link we can simply just click and view in our browsers is a huge help to those of us volunteering our time to assist in supporting MuseScore.
In reply to OK, I clicked those fileds… by Marc Sabatella
Did clean both machines from MuseScore. Registry, firewall, app screening.
As mentioned, one Win10, one Win11, one i3gen8 one i7gen12, no bloatware, no 3rd party sec soft. All working fine besides MuseScore.
Didn't help, all the same after another two hours spent. This is exactly what I was not planning to do. I cannot help it since I am not an expert, I am a paying user, and here I am again, just wasting your and my time.
Is there any other library base other than QT in MuseScore that could be an issue?
Will be back to 3.6 since I heard one can use the 4-files backwards by unzipping them.
Have a good one...
In reply to Did clean both machines from… by urhs
What a relief - 3.6 still works all fine on both my machines (that represent that "handful" of systems that seem unable to acommodate MuseScore4).
In reply to OK, I clicked those fileds… by Marc Sabatella
I think the file mapping routines are totally broken, that's why it won't work properly on systems that rely on OneDrive (to be able to work from different computers). MuseScore wildly creates folders and files no matter what it has been set up for or configured after installation and it does that every single time, when you call styles for example.
I tried to help it by replacing paths by %onedrive% to get around that and make it find everything. Well, it starts anyways to make new folders in "Documents", "AppData" and elsewhere, it even created folders with the name "%onedrive%". So it doesn't follow guidelines which results in the mentioned behaviour in tailored systems.
In reply to I think the file mapping… by urhs
I'm not following - OneDrive is normally set up by default, and if you haven't set up custom configurations, all works smoothly. The files that get created get created in the standard locations on first startup then not again,
I guess you've modified the defaults somehow. Could you share your steps so we can try to reproduce an issue? And does this somehow relate to the crash or to the Style dialog?
In reply to I'm, not following -… by Marc Sabatella
Sorry, I gave up, it just didn't matter, if it was a fresh clean install including a polished registry and all other files and folders being removed before, either the normal or portable version, it also didn't matter if I tried to help it with standard installation or relative or absolute path assignments, always the exact same effects. Of course I will be back checking with every major version bump... Thanks anyway, have a good one.
! I FOUND IT ! PLEASE SHARE !
It's "text cursor" within windows accessability
turn it OFF, restart, and you're done
also, "styles" now comes up faster, instantly on my win10 w/ i3 gen8, within 8s on my win11 w/ i7 gen12
feels like i won a war (casualties = time spent)
In reply to !!! I FOUND IT !!! PLEASE… by urhs
That's is all but one issue.
For me it makes a diff between 28 and 10 secs. The latter is certainly an improvement but still way too long
In reply to !!! I FOUND IT !!! PLEASE… by urhs
Interesting, thanks for the investigation for sharing the result. I'll add a comment to this effect on the GitHub issue(s), Does this affect the crash for you, or just the style dialog?
But still, 8 seconds is way too long for the style dialog as well. Something is still wrong. But this does give some ideas of places to look - maybe other accessibility settings.