Bug 227753 - [ Mac Debug ] fast/dom/Window/post-message-large-array-buffer-should-not-crash.html is a flaky failure
Summary: [ Mac Debug ] fast/dom/Window/post-message-large-array-buffer-should-not-cras...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: ayumi_kojima
Keywords: InRadar
: 227755 (view as bug list)
Depends on:
Reported: 2021-07-07 10:36 PDT by ayumi_kojima
Modified: 2021-09-09 13:06 PDT (History)
4 users (show)

See Also:

Patch (1.47 KB, patch)
2021-07-07 10:58 PDT, ayumi_kojima
no flags Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description ayumi_kojima 2021-07-07 10:36:16 PDT

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)
Comment 1 Radar WebKit Bug Importer 2021-07-07 10:37:27 PDT
Comment 2 ayumi_kojima 2021-07-07 10:58:06 PDT
Created attachment 433048 [details]
Comment 3 Truitt Savell 2021-07-07 11:04:55 PDT
Comment on attachment 433048 [details]

Clearing flags on attachment: 433048

Committed r279650 (239463@main): <https://commits.webkit.org/239463@main>
Comment 4 Ryan Haddad 2021-09-09 13:06:13 PDT
*** Bug 227755 has been marked as a duplicate of this bug. ***
Comment 5 Ryan Haddad 2021-09-09 13:06:43 PDT
Comment from Keith in the dupe:
We should probably just change the test to "handle" the promise, which can just be an empty callback.