Bug 598650 - Increase JSGC_MAX_MALLOC_BYTES to 128MB, r=gal
authorGregor Wagner <anygregor@gmail.com>
Mon, 01 Nov 2010 18:16:03 -0700
changeset 57676 9e7777fd1d197c72df1d2de0da3ca0d0d7969494
parent 57675 2098bd53381e97dfdf772c9e34e7353b6e24600d
child 57677 47729824b12cdbf93e3cb50dc18c2672b43a0645
push id1
push usershaver@mozilla.com
push dateTue, 04 Jan 2011 17:58:04 +0000
reviewersgal
bugs598650
milestone2.0b8pre
Bug 598650 - Increase JSGC_MAX_MALLOC_BYTES to 128MB, r=gal
dom/base/nsJSEnvironment.cpp
--- a/dom/base/nsJSEnvironment.cpp
+++ b/dom/base/nsJSEnvironment.cpp
@@ -3977,17 +3977,17 @@ SetMemoryHighWaterMarkPrefChangedCallbac
     /*
      * There are two ways to allocate memory in SpiderMonkey. One is
      * to use jsmalloc() and the other is to use GC-owned memory
      * (e.g. js_NewGCThing()).
      *
      * In the browser, we don't cap the amount of GC-owned memory.
      */
     JS_SetGCParameter(nsJSRuntime::sRuntime, JSGC_MAX_MALLOC_BYTES,
-                      64L * 1024L * 1024L);
+                      128L * 1024L * 1024L);
     JS_SetGCParameter(nsJSRuntime::sRuntime, JSGC_MAX_BYTES,
                       0xffffffff);
   } else {
     JS_SetGCParameter(nsJSRuntime::sRuntime, JSGC_MAX_MALLOC_BYTES,
                       highwatermark * 1024L * 1024L);
     JS_SetGCParameter(nsJSRuntime::sRuntime, JSGC_MAX_BYTES,
                       highwatermark * 1024L * 1024L);
   }