<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION(r208511): ImageDecoders: Crash decoding GIF images since r208511"
href="https://bugs.webkit.org/show_bug.cgi?id=164864#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION(r208511): ImageDecoders: Crash decoding GIF images since r208511"
href="https://bugs.webkit.org/show_bug.cgi?id=164864">bug 164864</a>
from <span class="vcard"><a class="email" href="mailto:simon.fraser@apple.com" title="Simon Fraser (smfr) <simon.fraser@apple.com>"> <span class="fn">Simon Fraser (smfr)</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=164864#c4">comment #4</a>)
<span class="quote">> Actually I named this m_decoderLock at first, but sounded redundant to me
> because the class is ImageDecoder. Maybe m_decodeLock, since we are
> protecting the decode() method in the end.</span >
Locks don't protect code, they protect data. m_lock is probably OK here.
What needs to happen to make the decoders thread safe?</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>