<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<meta http-equiv="Content-Style-Type" content="text/css" />
<meta name="generator" content="pandoc" />
<title></title>
<style type="text/css">code{white-space: pre;}</style>
</head>
<body>
<p>Hi Rémi,</p>
<p>On 2017-03-29 21:23, Rémi Denis-Courmont wrote:</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> Le keskiviikkona 29. maaliskuuta 2017, 19.41.53 EEST Filip Roséen a écrit :</code></pre>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> Hi Rémi,
On 2017-03-29 20:34, Rémi Denis-Courmont wrote:</code></pre>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> As ALREADY NOTED; this cannot possibly fix the bug in question.</code></pre>
</blockquote>
<pre><code> It fixes the issue described in ticket [#18151][1], which you closed as a
duplicate of [#17652][2]. I would be interested to see know how #18151 is
not fixed, as I did extensive testing and a lot of proof-reading to
inspect the relevant paths taken.</code></pre>
</blockquote>
<pre><code> I would be interested to know how a lock inversion can be fixed while not
settling for one lock order or the other, nor eliminating the code paths
leading to either orders.</code></pre>
</blockquote>
<p>As stated, you are the one who closed <code>#18151</code> as a duplicate of <code>#17652</code>; the ticket description for the former in detail describe what lock is being taken, and why it deadlocks.</p>
<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;color:#500050">
<pre><code> That it can´t be reproduced with the Qt, maybe. However that it is fixed
sounds logically impossible.</code></pre>
</blockquote>
<p>This was extensively tested with various setups, with and without <em>Qt</em> (as well as with other interfaces just for good measure). This has little to nothing to do with the interface used as it was very easily reproducible “without” (<code>-Idummy</code>) any interface at all.. as the problem lies in how clean-up is being done (which previously raced, as described in <code>#18151</code>).</p>
<p>/F</p>
</body>
</html>