Issue 674287 indicates that a 1-element std::deque uses 4KB on Android.

We use deques in the //net part of the WebSocket implementation:

1. std::deque<char> buffer_; in WebSocketDeflater
   Often will be several KB anyway, so not a problem?
2. std::deque<scoped_refptr<IOBufferWithSize> > in WebSocketInflater::InputQueue looks inefficient. Maybe short-lived?
3. std::queue<PendingReceivedFrame> pending_received_frames_; in WebSocketChannel will be inefficient if the renderer is slow.

The easiest thing would be to switch to std::list, but that's inefficient in its own ways.

WTF::Deque is not affected.