Hi Jens, 2015-09-24 18:11 GMT+02:00 Jens Radloff <[email protected]>: > Hi Andrew, hi Robert, > > To ensure that this behaviour is not caused by an "old" MusE folder in > ~/.config I removed the directory ~/.config/MusE and started MusE again, > so a new, fresh MusE folder in ~/.config got created. > > Background information: This "old" MusE folder in ~/.config is from my > installation of MusE 2.2.1, the last official release. I think Andrew told > me that, if I use a current clone version of MusE, then I need to remove > the old MusE folder in ~/.config to get a new version of this folder > created that is set up for the use of a current clone version of MusE. > > Let me add at this point that now, with a new, fresh MusE folder in > ~/.config, I do not have a "Out 1" track in any MusE song anymore which I > created so far. I think I reported this bug some months ago. > > So, as I wrote, I ensured that my clone installation of MusE is based on > a fresh MusE folder in ~/.config. > > But the behaviour can be still reproduced: MusE crashes when the > metronome button is activated at the moment when the play cursor reaches > the end of the loop region in this song test_song.med . > > So this behaviour does not seem to be caused by the content of the MusE > folder in ~/.config.
Ok, good so we can rule that out. > > This is the output of gdb (I could only copy what is shown in the > console): I only took a brief look but it seems the amount of information in the back trace is not much. Is the muse binary still built for release? Building it for debug may give more information. Some additional questions, sorry if you already answered before.. do you use a standard distribution? maybe we can reproduce your problem. what settings do you start jack with? The start of the printout below is what MusE outputs during running with -D, right? And you are starting MusE from within gdb? Unless you already did so I would suggest that you recompile MusE similar to the below: cmake .. -DCMAKE_BUILD_TYPE=debug make clean make make install Another thing you could try is to start MusE without plugins. and use MusEs own fluidsynth (under MESS) as audio output. muse2 -pNI2 We had for instance an issue some years ago that some plugins caused corruption in MusE memory space due to duplicated symbol names. /Robert ------------------------------------------------------------------------------ _______________________________________________ Lmuse-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lmuse-developer
