We added an AbortSignal (https://developer.mozilla.org/en-US/docs/Web/API/AbortSignal) to our frontend and noticed that Chrome started randomly crashing occasionally for engineers on our team.

At first we thought it was just bad luck, but after it kept happening after for a week we investigated. After managing to debug Chrome itself we narrowed it down to the 'abort' event on an AbortSignal. It seems that attaching an 'abort' handler in a certain way, and then aborting the signal, causes a hard crash of the content process.

Source code: https://github.com/calebj0seph/chrome-crash/blob/main/index....

Bug report: https://bugs.chromium.org/p/chromium/issues/detail?id=147273...