Greetings all, A few of us have found MusE to lock up our systems. I've had this problem since 0.6.3 running on 2.6.X and on a relatively new machine. I think I've run MusE successfully on this machine, but if I did, it was long ago. The symptoms are that the machine totally locks up and requires a hard reboot (reset), followed by ()fsck'ing all mounted drives on reboot. The CPU heats up as some sort of race condition occurs. It is not a kernel crash as has been suggested elsewhere, at least not for me; I wish it were. I found that I can set ulimit -l to some fraction of memory so that it isn't "unlimited." This does produce various warnings, but on this machine, with what little I've done thus far, MusE *seems* to run OK. It would seem to me, with what little I know about mlock() policy, that there is an mlock() SNAFU in some of the Linux audio programs. If that's not the case, I'd really like to hear the explanation. (Thanks to anyone who contributes info on this.) ulimit -l could very well be set to "unlimited" in many distributions rather than the distributors setting it to some sort of guess. Developers should count on it. I have a similar problem with qjackctl, but temporarily disabled memory locking entirely. I'll check it with ulimit set to some reasonable value. I believe that qamix also had this problem. I think that was it --- so far.... Thanks for your attention, and regards to everybody out there, Dave.