Receiving a large amount of frames in a short period causes StackOverflowException.

The overflow is caused by the recursive call of receive() in WebSocket.startReceiving().

private void startReceiving()
{
	if (_messageEventQueue.Count > 0)
		_messageEventQueue.Clear();

	_pongReceived = new ManualResetEvent(false);
	_receivingExited = new ManualResetEvent(false);

	Action receive = null;
	receive =
	  () =>
		WebSocketFrame.ReadFrameAsync(
		  _stream,
		  false,
		  frame =>
		  {
			  if (!processReceivedFrame(frame) || _readyState == WebSocketState.Closed)
			  {
				  var exited = _receivingExited;
				  if (exited != null)
					  exited.Set();

				  return;
			  }

			  // Receive next asap because the Ping or Close needs a response to it.
			  receive();

			  if (_inMessage || !HasMessage || _readyState != WebSocketState.Open)
				  return;

			  message();
		  },
		  ex =>
		  {
			  _logger.Fatal(ex.ToString());
			  fatal("An exception has occurred while receiving.", ex);
		  }
		);

	receive();
}

Any ideas on how to get rid of the recursion?

Start at WebSocket.startReceiving and WebSocketFrame.ReadFrameAsync, then trace how the callback schedules the next receive while processing a burst of frames. Reproduce the large-frame-rate case and verify that receiving completes without StackOverflowException while preserving Ping and Close handling.