Bug 227755

Summary: [ iOS Debug ] fast/dom/Window/post-message-large-array-buffer-should-not-crash.html is a flaky failure
Product: WebKit Reporter: ayumi_kojima
Component: New BugsAssignee: ayumi_kojima
Status: RESOLVED DUPLICATE    
Severity: Normal CC: keith_miller, tsavell, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: iPhone / iPad   
OS: Unspecified   
See Also: https://bugs.webkit.org/show_bug.cgi?id=227753
Attachments:
Description Flags
Update TestExpectations none

ayumi_kojima
Reported 2021-07-07 10:43:26 PDT
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 --- /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: RangeError: Out of memory. Check that trying to deserialize an ArrayBuffer when there's not enough memory does not crash (test may only fail flakily)
Attachments
Update TestExpectations (1.71 KB, patch)
2021-07-07 11:28 PDT, ayumi_kojima
no flags
Radar WebKit Bug Importer
Comment 1 2021-07-07 10:43:55 PDT
ayumi_kojima
Comment 2 2021-07-07 11:28:07 PDT
Created attachment 433052 [details] Update TestExpectations
Keith Miller
Comment 3 2021-07-07 11:29:12 PDT
We should probably just change the test to "handle" the promise, which can just be an empty callback.
Truitt Savell
Comment 4 2021-07-07 11:31:54 PDT
Comment on attachment 433052 [details] Update TestExpectations Clearing flags on attachment: 433052 Committed r279651 (239464@main): <https://commits.webkit.org/239464@main>
Ryan Haddad
Comment 5 2021-09-09 13:06:13 PDT
*** This bug has been marked as a duplicate of bug 227753 ***
Note You need to log in before you can comment on or make changes to this bug.