Comment 18 for bug 1719045

Revision history for this message
Marcelo Cerri (mhcerri) wrote :

Yes. Probably something in golang runtime is triggering the bug.

The last good version is 4.11.0-1004.4 and the problem still happens with 4.11.0-1005.5. 1005 comprehends just Bug #1707285, which introduced several changes. I'm restricting the bisect to it.