Mojo: Raise the message size limit.

content/app/mojo/mojo_init.cc

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/app/mojo/mojo_init.h"
 
 #include "base/memory/scoped_ptr.h"
+#include "mojo/edk/embedder/configuration.h"
 #include "mojo/edk/embedder/embedder.h"
 #include "mojo/edk/embedder/simple_platform_support.h"
 
 namespace content {
 
 void InitializeMojo() {
+  // Things like content_shell and DevTools ocassionally send big
+  // message which includes whole rendered screen or all loaded
+  // scripts. The buffer size has to be big enough to allow such use
+  // cases.
+  mojo::embedder::GetConfiguration()->max_message_num_bytes = 256*1024*1024;

[nasko, 2014/11/19 22:31:49]

I understand 4MB might be too small, but isn't 256MB a bit too much? Let's use
something that is a margin on top of the biggest message we've seen. I'd be more
comfortable with 32 or 64 to start with.

   mojo::embedder::Init(scoped_ptr<mojo::embedder::PlatformSupport>(
       new mojo::embedder::SimplePlatformSupport()));
 }
 
 }  // namespace content