Bug 81963 - WebProcess can get stuck in GC during many low memory signals
Summary: WebProcess can get stuck in GC during many low memory signals
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Mac Unspecified
: P2 Normal
Assignee: Stephanie Lewis
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-22 14:10 PDT by Stephanie Lewis
Modified: 2012-03-27 13:29 PDT (History)
2 users (show)

See Also:

Attachments
patch (2.59 KB, patch)
2012-03-23 17:07 PDT, Stephanie Lewis 		ggaren: review+
Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Stephanie Lewis 2012-03-22 14:10:09 PDT 
We have seen evidence of a computer getting stuck in GC during a low memory signal.  The GC was paging in more memory to run and so it was unable to finish before the next low memory signal fired.

We think with the new style of GC we will not get any value to forcing GC during a low memory signal so we should remove the call.

<rdar://problem/11094830> WebProcess appears to get stuck in its GC handler
Comment 1 Stephanie Lewis 2012-03-23 17:07:25 PDT 
Created attachment 133588 [details]
patch
Comment 2 Geoffrey Garen 2012-03-23 17:10:09 PDT 
Comment on attachment 133588 [details]
patch

r=me
Comment 3 Eric Seidel (no email) 2012-03-27 12:36:36 PDT 
Attachment 133588 [details] was posted by a committer and has review+, assigning to Stephanie Lewis for commit.
Comment 4 Stephanie Lewis 2012-03-27 13:29:58 PDT 
Committed http://trac.webkit.org/projects/webkit/changeset/111977