<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION (r182899): icloud.com crashes"
href="https://bugs.webkit.org/show_bug.cgi?id=143960#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION (r182899): icloud.com crashes"
href="https://bugs.webkit.org/show_bug.cgi?id=143960">bug 143960</a>
from <span class="vcard"><a class="email" href="mailto:ggaren@apple.com" title="Geoffrey Garen <ggaren@apple.com>"> <span class="fn">Geoffrey Garen</span></a>
</span></b>
<pre><span class="quote">> If the watchpointSet is null, it means there is no rare data and thus there
> shouldn't be an AllocationProfileWatchpoint for this node.</span >
OK. Sounds like an ASSERT is appropriate, then.
<span class="quote">> A least that was the case before I made the allocation profile clearing too
> aggressive when the .prototype is overwritten.
>
> This can only appear in the case of a singleton constructor whose prototype
> is overwritten after having been already constructed in the DFG, then
> constructed again, so no wonder the test cases did not catch this.
>
> I am writing a proper fix now.</span >
Nice!</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>