I suspect the bug is in the memblockq code somewhere. It seems like it wedges itself somehow. The "missing" state variable is something I'm looking at with suspicion. Why do we even have that? Can't we derive that from the other variables? Having redundant state is just asking for things to get out of sync and for bugs to appear. I added some tracing to memblockq in accordance with the attached patch. I've also attached the output from a run when this happens. If anyone else could also have a look I'd appreciate it. Rgds -- Pierre Ossman Software Development Cendio AB https://cendio.com Teknikringen 8 https://twitter.com/ThinLinc 583 30 Linköping https://facebook.com/ThinLinc Phone: +46-13-214600 https://plus.google.com/+CendioThinLinc A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? -------------- next part -------------- A non-text attachment was scrubbed... Name: memblockq-debug.patch Type: text/x-patch Size: 7194 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20160518/79e1471d/attachment-0001.bin> -------------- next part -------------- A non-text attachment was scrubbed... Name: dump.log.xz Type: application/x-xz Size: 695220 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20160518/79e1471d/attachment-0001.xz>
