Bug 609543 - Frequent hangs in dromaeo_sunspider during sunspider-access-nsieve.html (after sunspider-access-nbody.html); r=dmandelin a=blocking-beta9+
authorGregor Wagner <anygregor@gmail.com>
Tue, 30 Nov 2010 14:48:46 -0500
changeset 58392 5d4678e9fc37ea1400b6e40413ed194ff5f3af1b
parent 58391 0418174c85227aae8a056d0d39356b425e72e445
child 58394 0a4135190b4846e33bc2cff86d19f8b2bf365fd0
push id17279
push usereakhgari@mozilla.com
push dateTue, 30 Nov 2010 19:48:55 +0000
treeherdermozilla-central@5d4678e9fc37 [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewersdmandelin, blocking-beta9
bugs609543
milestone2.0b8pre
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 609543 - Frequent hangs in dromaeo_sunspider during sunspider-access-nsieve.html (after sunspider-access-nbody.html); r=dmandelin a=blocking-beta9+
dom/base/nsJSEnvironment.cpp
--- a/dom/base/nsJSEnvironment.cpp
+++ b/dom/base/nsJSEnvironment.cpp
@@ -3999,17 +3999,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,
-                      128L * 1024L * 1024L);
+                      80L * 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);
   }