RESOLVED FIXED 134711
WKProcessPoolConfigurationPrivate's maximumProcessCount property has no effect 
https://bugs.webkit.org/show_bug.cgi?id=134711
Summary WKProcessPoolConfigurationPrivate's maximumProcessCount property has no effect
Tim Horton
Reported 2014-07-07 19:06:52 PDT
Because nothing ever reads from it! It would also be nice if MiniBrowser had a maximumProcessCount=1 mode; frequently useful for debugging things where having two pages in one process is important.
Attachments
patch (1.52 KB, patch)
2014-07-08 12:19 PDT, Tim Horton 		mitz: review+
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Tim Horton
Comment 1 2014-07-07 20:00:30 PDT
Huh, I see no indication that there's a process cap by default. I thought it was 20 or some such?
Tim Horton
Comment 2 2014-07-08 12:19:57 PDT
Created attachment 234581 [details] patch
mitz
Comment 3 2014-07-08 12:22:38 PDT
Comment on attachment 234581 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=234581&action=review > Source/WebKit2/UIProcess/API/Cocoa/WKProcessPool.mm:173 > + _context->setMaximumNumberOfProcesses(configuration.maximumProcessCount); Everywhere else in this method we use the instance variable _configuration, not the parameter.
Tim Horton
Comment 4 2014-07-08 12:28:43 PDT
http://trac.webkit.org/changeset/170893
Note You need to log in before you can comment on or make changes to this bug.