2021-12-22 - FransKlip
forum: "MS hangs for about a minute after about any action"
answer on request:
    Jojo-Schmitz • Dec 22, 2021 - 12:20 new
    In reply to final update: system re… by fransklip
    Maybe you can compare those settings and find the culprit?
"

I've included 4 .ini files.
Compared 3 them using diff tool Meld
    "first-run" versus "good-after-2-days", and
    "prev-problematic" versus "good-after-2-days"
    MuseScore3-v362-t02-lockup-after-Show-Navigator

but could not see any strange things, only the differences that a retired programmer unfamiliar
with the file layout, would characterize as "looks normal".
About the binary entries I can't say anything.

FILES:

MuseScore3-prev-problematic
    the file last used on previous system, using alsa audio,
    this file was copied to the newly installed system and a copy renamed
    to MuseScore.ini for testing, which gave again the errors on almost every action

MuseScore3-v362-first-run.ini
    the file after first time start of Musescore v3.6.2 and having loaded a test song,
    a simple test (playback, click edit a note, show props) and then closed MS.
    No other settings changed, still using default audio out.

MuseScore3-v362-good-after-2-days
    the file based on 'first-run' after some normal use of v362.

MuseScore3-v362-t02-lockup-after-Show-Navigator
    the file after Show Navigator resulted for the 3rd time in a lock-up,
    this time did it immediately after app (normal) startup.

MuseScore3-v362-t03-defaults-one-song-loaded
    after 'preferences - reset to defaults' and loaded one song from the 'recent files' list


THE LOCK-UP REAPPEARED when showing Navigator, and getting worse
----------------------
Just before this text I experienced again the same lock-up. Now this was after a short period of blanked screen
(no sleep mode) after which I was playing with opening and closing some less-used views "synth" and "navigator"
to match the default volume with other audio sources.
After a system reboot MS opened fast with the previous restored session having 3 songs open, and again Show Navigator
now as first action, started a lock-up of a minute (69 .. 70 secs).
Seems to be repeatable now. Closing the Navigator gave no lock-up.

After using MS for normal use (play 2 lesson songs, try parts of a new song, some editing to a new one in preparation),
it looks like the chances for a lock-up increase, at first sometimes on playback start, later on when switch to another song,
more later on touching a note to edit it.
Lock-up on showing Navigator now is repeatable, even as first thing to do after startup, which still loads the 3 or 4 files
of the previous session wihtin 1..2 seconds.

THE LOCK-UP DISAPPEARED after Reset Preferences to Default
----------------------
Then did "Preferences: Reset to default", and restarted MS.
The problems seem to have disappeared !!
Then applied some necessary settings: jack audio, startup with last session.
Forunately some useful things are retained: the "recent files list, the keyboard settings (the much-used [ and ] for
loop-start and loop-end that have disappeared from installation default, though the action name still mentions them as hot keys)
Saved the settings file just before and after the reset.

This is a simple work-around!
Just have to redo a few settings. And do NOT abort MS but wait for a minute, else your "recently used files" list fills up
with internal, unrecognisable recovery filenames.

Used this morning MS for playing half an hour on 3 songs. No problems.


This kind of strange problems gradually building up in time, makes me think of some other shortage of a limited resource,
e.g. a memory leak, some removed objects that are not freed. But it builds up across program restarts and OS reboots.
And doing Reset Preferences clears the situation.

Could this be related to the appimage environment? That is a virtual drive of limited size.