Frédéric Brière

For the record, here's where I think the bug is located (with another copy in `snd_pcm_mmap_read_areas()`): https://github.com/alsa-project/alsa-lib/blob/81a7a93636d9472fcb0c2ff32d9bfdf6ed10763d/src/pcm/pcm_mmap.c#L86-L90 `__snd_pcm_mmap_begin()` is called to set up `pcm_areas` (on the stack), but no check...

@cyberbeat Do you get the same "failed assertion" message? If so, would you be able to generate a backtrace as I have explained in my previous comment? Thanks!

> Finally a backtrace: > > ``` > #6 0x00007fd405b51f89 in ?? () from /usr/lib64/alsa-lib/libasound_module_pcm_pipewire.so > ``` Drat! I did not expect PipeWire to show up this early in the...

@urbanware-org Like in my reply to @cyberbeat above, I also suggest you install the `debuginfo` packages for `pipewire-libs` and `pipewire-alsa`, just to be safe.

> Now with all debug-info-packages (also pipewire libspa-support), using pipewire 0.3.82, libasound 1.2.6.1 Thanks! I have opened an [issue](https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3600) on the PipeWire tracker.

> So, Twinkle crashed once today and I can finally provide the backtrace. Weird, your backtrace contains function names, but lacks argument values and line numbers. First time I've seen...

> Yes, I already use 0.3.84, and did not have any crash until now. Many thanks @fbriere ! Glad to hear it, and you're welcome!