[Webkit-unassigned] [Bug 61137] New: Don't allocate 1Gb at startup on x86_64 && !Linux

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=61137

           Summary: Don't allocate 1Gb at startup on x86_64 && !Linux
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
        OS/Version: Other
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: landry at openbsd.org


Followup to https://bugs.webkit.org/show_bug.cgi?id=53352 and https://bugs.webkit.org/show_bug.cgi?id=53401.

In WebkitGtk 1.4.0 (which was recently commited to OpenBSD's portstree), on OpenBSD/amd64 at startup webkit browsers preallocate 1Gb of ram, which is more than the default value for ulimit (512mb), so they quickly explode.

#if CPU(ARM)
typedef PageTables16MB FixedVMPoolPageTables;
#elif CPU(X86_64)
typedef PageTables1GB FixedVMPoolPageTables;
#else
typedef PageTables32MB FixedVMPoolPageTables;
#endif

>From my understanding of the comments in bug 53352 (i might be wrong), the 1Gb allocation on X86_64 is done to allow huge regressions tests to pass fine on linux/x86_64. While i won't debate on that particular point, could it be made to be linux-only, so that we don't have to patch that code to remove that insane greedy allocation ?

Ie as of now, we apply http://www.openbsd.org/cgi-bin/cvsweb/ports/www/webkit/patches/patch-Source_JavaScriptCore_jit_ExecutableAllocatorFixedVMPool_cpp?rev=1.1 to workaround that.

Maybe it could be commited as #elif CPU(X86_64) && OS(LINUX), so that defaults are more sane ?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.