| Summary: | REGRESSION(262909@main): [ iOS ] TestWebKitAPI.WebKit.LockdownModeDefaultFirstUseMessage is a flaky crash | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Robert Jenner <jenner> | ||||
| Component: | New Bugs | Assignee: | youenn fablet <youennf> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | webkit-bot-watchers-bugzilla, webkit-bug-importer, youennf | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=254958 | ||||||
| Attachments: |
|
||||||
|
Description
Robert Jenner
2023-05-03 14:13:02 PDT
I was able to reproduce the crash at iOS 16 Debug ToT running the test as follows: run-api-tests TestWebKitAPI.WebKit.LockdownModeDefaultFirstUseMessage --iterations 100 I believe I was able to bisect to a specific regression point, but I am still confirming. However, so far it appears that https://commits.webkit.org/262909@main may have caused this to occur. I have been able to successfully reproduce the Segmentation fault crash mentioned above at 262909@main, but I was not able to reproduce it at 262908@main. I'm going to run the test in a few more iterations, just to confirm. https://commits.webkit.org/262909@main does appear to have changes in it that impact lockdown mode, and since this is a lock down mode test, I believe that is the cause for this. Also, I wasn't able to reproduce the crash at 262908@main, so it does Created attachment 466199 [details]
crash log
*** Bug 256513 has been marked as a duplicate of this bug. *** Pull request: https://github.com/WebKit/WebKit/pull/13631 Committed 263865@main (83e11a3a6c03): <https://commits.webkit.org/263865@main> Reviewed commits have been landed. Closing PR #13631 and removing active labels. |