[Webkit-unassigned] [Bug 28676] New: Safari 4 not releasing memory back to the operating system

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Mon Aug 24 02:10:34 PDT 2009


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

           Summary: Safari 4 not releasing memory back to the operating
                    system
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: PC
               URL: http://farm3.static.flickr.com/2552/3851167461_d56de44
                    d47_o.png
        OS/Version: Windows XP
            Status: UNCONFIRMED
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: jaffathecake at gmail.com


Once Safari has claimed memory from the operating system, it doesn't seem to
give it back, even though it's no longer using it.

Running the first test on the following page
http://www.jakearchibald.co.uk/jsperformance/closurememory/1.html, this creates
a 1mb string every second.

http://www.flickr.com/photos/jaffathecake/3851167461/sizes/o/

Chrome (and other browsers) release the memory back to the operating system
when the test is ended, whereas Safari keeps it, even if the tab is closed.
Safari will reuse the memory it has reserved, but it doesn't give it back to
the operating system, even if it has claimed 700mb+.

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



More information about the webkit-unassigned mailing list