Comment 5 for bug 491329

I can reproduce it though. It looks like libasound calls some pulseaudio code, which is where the bus error occurs:

loading driver ..
apparent rate = 44100
creating alsa driver ... hw:0|hw:0|256|2|44100|0|0|nomon|swmeter|-|32bit
control device hw:0

Program received signal SIGBUS, Bus error.
pa_atomic_load () at ./pulsecore/atomic.h:57
57 ./pulsecore/atomic.h: No such file or directory.
        in ./pulsecore/atomic.h
(gdb) where
#0 pa_atomic_load () at ./pulsecore/atomic.h:57
#1 pa_shm_cleanup () at pulsecore/shm.c:370
#2 0x00e7dfed in pa_shm_create_rw (m=0x8086f18, size=67108864, shared=true, mode=448) at pulsecore/shm.c:109
#3 0x00e7024f in pa_mempool_new (shared=false, size=0) at pulsecore/memblock.c:731
#4 0x00d738a4 in pa_context_new_with_proplist (mainloop=0x807cca8, name=0xd19993 "Alsa hook", p=0x0) at pulse/context.c:199
#5 0x00d7398c in pa_context_new (mainloop=0x807cca8, name=0xd19993 "Alsa hook") at pulse/context.c:116
#6 0x00d1987d in conf_pulse_hook_load_if_running () from /usr/lib/alsa-lib/libasound_module_conf_pulse.so
#7 0x004e43d7 in ?? () from /usr/lib/libasound.so.2
#8 0x004e49c5 in snd_config_searcha_hooks () from /usr/lib/libasound.so.2
#9 0x004e4b14 in snd_config_searchva_hooks () from /usr/lib/libasound.so.2
#10 0x004e4caa in ?? () from /usr/lib/libasound.so.2
#11 0x004e4e7b in snd_config_search_definition () from /usr/lib/libasound.so.2
#12 0x004f2dbd in ?? () from /usr/lib/libasound.so.2
#13 0x00fa3de9 in ?? () from /usr/lib/jack/jack_alsa.so
#14 0x00fa615c in driver_initialize () from /usr/lib/jack/jack_alsa.so
#15 0x00dc1110 in jack_engine_load_driver () from /usr/lib/libjackserver.so.0

It's a bit odd that ALSA calls PulseAudio code at all, but if there's enough memory available this doesn't appear to be a problem.

Looks like when SHM memory is low, PulseAudio gets confused.