fast/dom/Window/post-message-large-array-buffer-should-not-crash.html History: https://results.webkit.org/?suite=layout-tests&test=fast%2Fdom%2FWindow%2Fpost-message-large-array-buffer-should-not-crash.html I was able to reproduce the failure at r279603 and r276913 with run-webkit-tests fast/dom/Window/post-message-large-array-buffer-should-not-crash.html --iterations 50 —debug -f -1 --- /Volumes/Data/Builds/debug-279603/layout-test-results/fast/dom/Window/post-message-large-array-buffer-should-not-crash-expected.txt +++ /Volumes/Data/Builds/debug-279603/layout-test-results/fast/dom/Window/post-message-large-array-buffer-should-not-crash-actual.txt @@ -1,3 +1,4 @@ +CONSOLE MESSAGE: Unhandled Promise Rejection: RangeError: Maximum call stack size exceeded. Check that trying to deserialize an ArrayBuffer when there's not enough memory does not crash (test may only fail flakily)
<rdar://problem/80277602>
Created attachment 433048 [details] Patch
Comment on attachment 433048 [details] Patch Clearing flags on attachment: 433048 Committed r279650 (239463@main): <https://commits.webkit.org/239463@main>
*** Bug 227755 has been marked as a duplicate of this bug. ***
Comment from Keith in the dupe: We should probably just change the test to "handle" the promise, which can just be an empty callback.