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.