<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Add API to set the maximum number of web processes per WebKitWebContext"
href="https://bugs.webkit.org/show_bug.cgi?id=147108#c6">Comment # 6</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - [GTK] Add API to set the maximum number of web processes per WebKitWebContext"
href="https://bugs.webkit.org/show_bug.cgi?id=147108">bug 147108</a>
from <span class="vcard"><a class="email" href="mailto:cgarcia@igalia.com" title="Carlos Garcia Campos <cgarcia@igalia.com>"> <span class="fn">Carlos Garcia Campos</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=147108#c3">comment #3</a>)
<span class="quote">> The crash is good; it prevents programmers from screwing up and calling it
> too late. This isn't the only place we do that (I think for set process
> model, for example).</span >
Right, we (WebProcessPool actually) has some CRASH calls in setProcessModel and setMaximumNumberOfProcesses. We can prevent this by making process model and web process count limit construct-only properties, but that makes the API less convenient and doesn't allow to change them for the default context.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>