Dear Roberto, So sorry for the unreasonably long wait for a reply! I confess to taking a winter break from Debian around the time of your reply, and then I was negligent in following up on non-RC bugs. Sorry :-/
Reply follows inline: Roberto <robe...@zenvoid.org> writes: > Hi, thank you for adopting Hydrogen :) > > Yes, it still happens with 0.9.7-6 (not tried upstream git sources). > We now have the option of 1.0.1-3 on Bullseye (Debian 11) :-) When you have the time to upgrade to Bullseye, would you please update this bug with your experience. > Maybe the severity can be lowered, I've been using Hydrogen with the > workaround of choosing samples in advance, never deleting layers when > building an instrument, and it works. It seems that deleting a layer is > the most risky task, probably when the sound is still playing. > That sounds like an unnecessarily cumbersome workaround, and I agree that this bug is important :-) If two or more people could reproduce the crash then I'd say it was an RC bug. For what it's worth, I believe that a hard to reproduce crash is *always* an important bug. > Can't you reproduce it? It only took a few seconds to crash it, just a > minute before writing this email. If this only happens to me, we could > close the bug, though I wonder why are only my computers triggering the > crash :/ I'm not sure why it crashes your system but not mine. For what it's worth, here is the setup on the system I record with: Jackdbus + the PulseAudio jack bridge + custom 5.4 realtime kernel + Scarlett 2i2 (1st gen) + rtirq. I wonder if the reason you're able to trigger this issue (I agree with your assessment and hypothesis, by the way) is because your interface is taking slightly longer to process the packets/stream, leading to a race->crash rather than a benign race? If so, you have a great setup for audio bug hunting! :-D If you're comfortable installing individual packages from experimental, and you're also able to reproduce the crash with 1.0.1-3 in Bullseye, then would you please consider also testing 1.1.0~beta1-1~exp1 (from experimental) to see if it's also affected? If 1.1.0~beta1 is affected then we'll need to contact upstream without delay, in the hopes of getting the fix into the next stable release. Kind regards, and sorry again for taking so long to reply, Nicholas
signature.asc
Description: PGP signature
