| Summary: | REGRESSION (r275038?): Perf test IndexedDB/stress/large-binary-keys.html failing with logging about memory pressure events | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Ryan Haddad <ryanhaddad> | ||||
| Component: | New Bugs | Assignee: | Chris Dumez <cdumez> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | achristensen, benjamin, cdumez, cmarcelo, darin, ews-watchlist, ggaren, webkit-bot-watchers-bugzilla, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=223717 | ||||||
| Attachments: |
|
||||||
|
Description
Ryan Haddad
2021-03-26 16:16:07 PDT
https://trac.webkit.org/changeset/275038/webkit looks like it could have been related Created attachment 424418 [details]
Patch
Comment on attachment 424418 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=424418&action=review > Source/WTF/ChangeLog:10 > + Use RELEASE_LOG() instead of WTFLogAlways() to log memory pressure events, so that they don't > + show on stdout in the performance tests and make them fail. Does this still achieve what we want in production builds? (In reply to Darin Adler from comment #4) > Comment on attachment 424418 [details] > Patch > > View in context: > https://bugs.webkit.org/attachment.cgi?id=424418&action=review > > > Source/WTF/ChangeLog:10 > > + Use RELEASE_LOG() instead of WTFLogAlways() to log memory pressure events, so that they don't > > + show on stdout in the performance tests and make them fail. > > Does this still achieve what we want in production builds? We will see the logging is os_log which I believe is suitable for such logging. Committed r275125: <https://commits.webkit.org/r275125> All reviewed patches have been landed. Closing bug and clearing flags on attachment 424418 [details]. |