<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - library should be thread-safe"
href="https://bugs.freedesktop.org/show_bug.cgi?id=50992#c101">Comment # 101</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - library should be thread-safe"
href="https://bugs.freedesktop.org/show_bug.cgi?id=50992">bug 50992</a>
from <span class="vcard"><a class="email" href="mailto:Thomas.Freitag@alfa.de" title="Thomas Freitag <Thomas.Freitag@alfa.de>"> <span class="fn">Thomas Freitag</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=50992#c100">comment #100</a>)
<span class="quote">> Sure, that if might fix the crash, but the question of why that variable is
> null (unlike when not using multiple threads that has a correct value) still
> remains, no?</span >
May be. But in a diff of the rendered output I didn't see any changes, as far
as I remember. And that is what the patch should do: parallel rendering pages
without changing output.
And one other comment to it: why could widget->getWidgetAnnotation() return a
NULL pointer at all?
But I think it's even too late to commit this patch, so I'll have time enough
to look at it.</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>