UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36

Steps to reproduce the problem:
Filing this from a discussion with dalecurtis@ here: https://codereview.chromium.org/2908073002/#msg91

The CL made it possible to create audio streams with buffer sizes between the min/max buffer sizes for each platform, however in the Pulse case trying to create a stream with the Pulse-specific max buffer size of 8192 resulted in failures in the FYI builds, more info here:

https://bugs.chromium.org/p/chromium/issues/detail?id=708917#c6

What appears to be happening is that in pulse_output.cc:136 (where the CHECK fails) we want to create a Pulse buffer of the required size, which in this case is 65536 (8192 frames per buffer * 2 bytes per sample * 4 channels). However Pulse internally has a max memory pool block size of 65536 - 64 (size of the block header) = 65472, which is the size returned by pa_stream_begin_write() and reported by the failing test.

dalecurtis@ says: Fixing the pulse code is the right thing to do if we want these new buffer sizes to be supported there. On very rare occasion someone hits that check with the current buffer sizes, so that's another reason for fixing the pulse code.

For now the Pulse-related changes were removed from the referenced CL but could be re-added once the underlying Pulse issue is fixed.

What is the expected behavior?

What went wrong?
Crash on the a Linux FYI build machine.

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 59.0.3071.115  Channel: stable
OS Version: OS X 10.12.5
Flash Version: