https://blog.ast.moe/en/tags/promise/Recent posts: GorimuchuHugohttps://blog.ast.moe/en/blog/2026-09-10-4/Thu, 10 Sep 2026 20:37:07 +0900https://blog.ast.moe/en/blog/2026-09-10-4/<p>While running Boa’s Test262, the test occasionally failed with exit code 134.</p> <p>The logs show the following errors:</p> <div class="highlight"><pre tabindex="0" style="color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>malloc(): unsorted double linked list corrupted </span></span></code></pre></div><p>The issue is the “normal Test262 release run is aborted due to an allocator consistency error” (<a href="https://github.com/ieee0824/omoikane/issues/638">issue #638</a>).</p> <p>At first, I assumed some recent change was corrupting memory somewhere. However, because Test262 runs a large number of tests in parallel, the logs alone don’t reveal which specific test is causing the problem.</p>