Bug 1271102 - Revert back to 256 MiB message limit. r=billm, a=lizzard
authorJ. Ryan Stinnett <jryans@gmail.com>
Tue, 24 May 2016 16:33:17 -0500
changeset 339643 d7a911ef57ad6b836046532794014cc06d24c6f2
parent 339642 81216130eacc2d0e96a4e6a19119cea6e7d0507f
child 339644 a7e4bbe5ec84cc2bb4e45ecd62de26292aa3adf6
push id6249
push userjlund@mozilla.com
push dateMon, 01 Aug 2016 13:59:36 +0000
treeherdermozilla-beta@bad9d4f5bf7e [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersbillm, lizzard
bugs1271102
milestone49.0a2
Bug 1271102 - Revert back to 256 MiB message limit. r=billm, a=lizzard 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,
   };