Bug 222003

Summary: [ macOS Debug Wk 2 ] imported/w3c/web-platform-tests/wasm/jsapi/functions/entry.html is flakey crashing
Product: WebKit Reporter: Robert Jenner <jenner>
Component: JavaScriptCoreAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: bfulgham, graouts, webkit-bot-watchers-bugzilla, webkit-bug-importer
Priority: P2 Keywords: InRadar
Version: WebKit Nightly Build   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
222003 stderr text file none

Robert Jenner
Reported 2021-02-16 15:06:24 PST
imported/w3c/web-platform-tests/wasm/jsapi/functions/entry.html is flakey crashing in macOS Debug on Wk 2. HISTORY URL: https://results.webkit.org/?suite=layout-tests&test=imported%2Fw3c%2Fweb-platform-tests%2Fwasm%2Fjsapi%2Ffunctions%2Fentry.html&platform=mac CRASH TEXT: No crash log found for GPUProcess:3439. stdout: stderr: LEAK: 2 WebPageProxy
Attachments
222003 stderr text file (220 bytes, text/plain)
2021-02-16 15:16 PST, Robert Jenner 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2021-02-16 15:06:46 PST
<rdar://problem/74408530>
Robert Jenner
Comment 2 2021-02-16 15:16:01 PST
Created attachment 420546 [details] 222003 stderr text file
Robert Jenner
Comment 3 2021-02-16 15:17:55 PST
Was able to produce a failure at tip of tree using test: run-webkit-test imported/w3c/web-platform-tests/wasm/jsapi/functions/entry.html --debug --iterations 1000 -f STDERR TEXT: 2021-02-16 15:14:46.467 com.apple.WebKit.WebContent.Development[33669:788375] IORegisterForSystemPower failed 2021-02-16 15:14:46.467 com.apple.WebKit.WebContent.Development[33669:788375] IORegisterForSystemPower failed
Robert Jenner
Comment 4 2021-02-16 15:20:12 PST
Starting on Antoine who last modified the JS API in r272904.That's also when the first crash occurred. CHANGESET URL: https://trac.webkit.org/changeset/272904/webkit
Antoine Quint
Comment 5 2021-02-17 09:15:10 PST
If this reproduces standalone as you suggest, this must be a JSC issue presuming this test is WASM only. Can you attach a crash log?
Note You need to log in before you can comment on or make changes to this bug.