And I did clearly say that crashing and data-corruption bugs were the ones I was interested in. However, considering the fact that I use Non every single day and haven't encountered this, I suspect that if the problem really exists, it must lie somewhere outside of the domain I have control over. Particularly the part about rebooting. Sometimes JACK will hang, but I've got nothing to do with that, and even in that case just killing JACK and restarting it should be sufficient.
I actually did experience something similar recently, but it had nothing to do with my software or anyone else's: My video card was failing and taking the computer down with it (buying a new card fixed the problem). I also had something similar happen on my laptop but it turned out that disabling the PSR feature of the intel video driver was all that was required. People always blame the software they're using at the moment of a crash, but IME, hard system lockups and crashes are almost never caused by a unix process, it's far more likely to be a hardware/driver/subsystem thing. Anyway, I'm probably wasting my time talking about it because the whole thing is probably just an attempt at trolling. On Wed, Jan 27, 2021 at 4:41 PM John Rigg <[email protected]> wrote: > On Wed, Jan 27, 2021 at 03:28:09PM +0100, Philipp Mueller wrote: > > I have to soft > > restart my laptop ever other week since either `non-timeline` or > > `non-mixer` did became a zombie process or because `non-timeline` > > did already bricked two sessions since the last updates. > > A proper bug report would be useful, and I doubt it would get > a hostile reception. In the ~7 years I've used Non as my main > DAW I've submitted several bug reports, a couple of minor > patches, and had a couple of feature requests accepted. All > of this was dealt with pleasantly and efficiently (no surprise, > as I try to avoid wasting developers' time with out-of-scope > feature requests or half-baked bug reports). > > John > > > >
