[pulseaudio-tickets] [Bug 45373] New: [alsa-sink] memblockq.c: Assertion '!bq->blocks || (bq->write_index + (int64_t)chunk.length <= bq->blocks->index)' failed at pulsecore/memblockq.c:408, function pa_memblockq_push(). Aborting.

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=45373

             Bug #: 45373
           Summary: [alsa-sink] memblockq.c: Assertion '!bq->blocks ||
                                     (bq->write_index +
                    (int64_t)chunk.length <= bq->blocks->index)' failed at
                    pulsecore/memblockq.c:408, function
                    pa_memblockq_push(). Aborting.
    Classification: Unclassified
           Product: PulseAudio
           Version: unspecified
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: core
        AssignedTo: pulseaudio-bugs at lists.freedesktop.org
        ReportedBy: tanuk at iki.fi
         QAContact: pulseaudio-bugs at lists.freedesktop.org
                CC: lennart at poettering.net


Created attachment 56298
  --> https://bugs.freedesktop.org/attachment.cgi?id=56298
Backtrace

Reported in IRC:

19:28 -!- jelly-home [~jelly at homestuck.iskon.hr] has joined #pulseaudio
19:30 < jelly-home> Hello, I've caught pulseaudio killing itself with a SIGABRT
and "Jan 29 15:44:43 kanta-linux pulseaudio[11171]: [alsa-sink] memblockq.c:
Assertion '!bq->blocks || 
                    (bq->write_index + (int64_t)chunk.length <=
bq->blocks->index)' failed at pulsecore/memblockq.c:408, function
pa_memblockq_push(). Aborting."
19:30 < jelly-home> attempt at getting a backtrace:
http://paste.debian.net/153989/
19:30 <@pulsator> Title: debian Pastezone (at paste.debian.net)
19:34 < jelly-home> this is PA 1.1, package 1.1-2 from Debian testing, i386
arch

I'll attach the backtrace here in case the pastebin link gets stale.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.