today i fixed the last to-me-known valgrind error (invalid read/write)
(btw, this reduced the unfiltered count of errors by two orders of
magnitude! 24000 errors vs multiple millions before!)
i'm pretty sure however that i haven't found them all, as i don't really
and even if i did, i cannot run muse through valgrind and really use it,
my machine is just too slow.
in the hope that yours is faster, i'd like you to really do a muse
session through valgrind (not just playing around like me ;) )
i know that it will be pretty slow and probably a bit painful. but if we
find more errors by this, this makes hard-to-track errors pretty easy to
fix, saving us and you (as user) a lot of pain ;)
(you might want to consider not using synthis etc, depends on how fast
you also might want to increase your jack buffer size, as valgrind may
be a bit non-realtime ;)
but i don't know, never used valgrind for an almost-realtime program.
please run the following:
valgrind --error-limit=no muse2 [your muse arguments] 2>&1 | tee
muse will take pretty long (several minutes here) to start, but run much
faster after that (still slow however. especially file dialogs take
the line above might not work. muse may just exit. in this case, prefix
it with "sudo", or run it as root in any other way. then it'll work.
please, try to _really_ use muse for everything you (or other musicians)
if you want, have the space and the time, you also might want to hjave
the valgrind console window in sight all the time, and note down which
error happened when you triggered which GUI operation. narrows down
problems a bit.