The non-working case loops continuously through creating and freeing
inputs just under 21 times/second.
It's not clear to me whether this is a Chrome bug or a Pulseaudio bug.
Any help in determining which one is the cause would be appreciated.
--
You received this bug notification because you
Public bug reported:
When I begin playback in Chrome while using Pulseaudio, I get only
cracking noises in my headphones, no original audio. Playback works
correctly with e.g. aplay, mplayer, Firefox's plugin-container for
Flash.
If I unplug and replug the device several times, it will start
** Attachment added: "pulseaudio verbose log for working case"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1605388/+attachment/4704958/+files/pulseverbose-working.log
** Description changed:
When I begin playback in Chrome while using Pulseaudio, I get only
cracking noises
Public bug reported:
When using a heavy plugin (e.g. unite, ctrlP, many others), vim's GC is
stressed. vim's GC has a performance bug which causes it to be O(n^2),
which results in vim freezing up when it runs. This is fixed in a newer
version of vim. This patch should be considered for
4 matches
Mail list logo