Bug 1271102 - Revert back to 256 MiB message limit. r=billm draft
authorJ. Ryan Stinnett <jryans@gmail.com>
Tue, 24 May 2016 16:33:17 -0500
changeset 376377 f26c71ca7c0ba4d947933a14c688cf0fdcb81487
parent 376376 fb0507f42e74128627a5fad0c82d5f1cbe435d93
child 523131 480512a3bff6f1e9eef99d3a0a5efcbccc6dce2e
push id20555
push userbmo:jryans@gmail.com
push dateTue, 07 Jun 2016 20:27:09 +0000
reviewersbillm
bugs1271102
milestone50.0a1
Bug 1271102 - Revert back to 256 MiB message limit. r=billm It appears to be hard to fix some sources of >128 MiB messages (e.g. IndexedDB), so revert back to a 256MiB limit for the short term. MozReview-Commit-ID: Jg2tJnqWOtd
ipc/chromium/src/chrome/common/ipc_channel.h
--- a/ipc/chromium/src/chrome/common/ipc_channel.h
+++ b/ipc/chromium/src/chrome/common/ipc_channel.h
@@ -45,17 +45,17 @@ class Channel : public Message::Sender {
   enum Mode {
     MODE_SERVER,
     MODE_CLIENT
   };
 
   enum {
     // The maximum message size in bytes. Attempting to receive a
     // message of this size or bigger results in a channel error.
-    kMaximumMessageSize = 128 * 1024 * 1024,
+    kMaximumMessageSize = 256 * 1024 * 1024,
 
     // Ammount of data to read at once from the pipe.
     kReadBufferSize = 4 * 1024,
 
     // Maximum size of a message that we allow to be copied (rather than moved).
     kMaxCopySize = 32 * 1024,
   };