pulseaudio assertions failing with pygame

Bug #1451614 reported by Yoan
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Linux Mint
New
Undecided
Unassigned

Bug Description

I've noticed regular -but hard to reproduce- pulseaudio bugs when using the pygame module for python 2.7.

1) Assertion 't = find_next_time_event( m )' failed at pulse/mainloop.c:721, function calc_next_timeout() . Aborting .

2) Assertion 'e->mainloop->n_enabled_defer_events > 0' failed at pulse/mainloop.c:260, function mainloop_defer_enable(). Aborting. [I've currently a gdb paused after SIGABRT on this assertion, if I can provide a trace or something useful tell me before I reboot...]

3) At some point during execution of a python script some thread suddenly starts using 100% of CPU, sounds (if any) stop playing while everything else continues working. Since I don't manage to catch an obvious CPU burner with python's profiler (cProfile) I assume it comes from a C extension. I've identified the faulty thread with gdb and top -H:
 Thread 0x7fffe1507700 (LWP 19065) "python" 0x00007ffff59e8466 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0

btw, assertion 1) happens very often but 2) just once (20 minutes ago) after I've updated pygame to a later version and compiled it with symbols to debug these with gdb.

pygame.__version__ = '1.9.1release'
python --version Python 2.7.6
pulseaudio --version = pulseaudio 4.0
uname -a = Linux e6410 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/issue = Linux Mint 17 Qiana

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.