Skip to content
Tech News
← Back to articles

Developer fixes WebKit bug causing some JavaScript promises to hang forever

read original more articles
GoKawiil Brief

A bug hunter found that a crafted JavaScript program using Promise.resolve() and a throwing Symbol.species getter would never finish running in Safari 26 and Bun 1.3.14, both of which use Apple's JavaScriptCore engine, while Node.js correctly threw an error. The author traced the fault to WebKit bug 318399, where the promise was left neither fulfilled nor rejected, and submitted a 16-line patch (WebKit/WebKit#68749) to resolve it.

Why It Matters

GoKawiil's interpretation of the reporting above, not reported fact.

The bug shows how subtle deviations from the ECMAScript specification can cause real runtimes to silently freeze instead of erroring, which could make debugging asynchronous code in Safari or Bun unexpectedly difficult. Because JavaScriptCore powers both Safari and Bun, a single spec compliance gap can affect multiple widely used platforms at once, underscoring the value of cross-engine conformance testing.

Key Takeaways

Source: alistair.sh, 2026-11-14

Published there as: “Fixing a WebKit bug to see if promises are made of train tracks”

Read the original report → The summary and analysis above are GoKawiil's own, written from reporting by the source above. Facts and quotes belong to the original publisher.
Keep reading
webkit 17 briefs → bun 6 briefs →