<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - currentThreadIsHoldingLock Heap::unprotect Assertion"
href="https://bugs.webkit.org/show_bug.cgi?id=159579#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - currentThreadIsHoldingLock Heap::unprotect Assertion"
href="https://bugs.webkit.org/show_bug.cgi?id=159579">bug 159579</a>
from <span class="vcard"><a class="email" href="mailto:chris.vno@outlook.com" title="Chris Vienneau <chris.vno@outlook.com>"> <span class="fn">Chris Vienneau</span></a>
</span></b>
<pre>Before I worry about getting it into trunk, I'm more interested in some inspection. Am I out to lunch on this change? I like to think that JSLock is well tested, so I would expect the error is on our end. However attempting to restore to similarly older implementation seems to make the problems go away. There is the chance that though it has been some time, a knock on has been lingering since it changed; of course there is the other possibility that the old implementation had incorrect behavior we relied on. I guess i'm asking if someone with good knowledge of this code can take a peek at it and comment.</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>