Summary: | REGRESSION [ Mac wk2 ] Tests are jetsamming: Unable to shrink memory footprint of process below the kill thresold [sic] | ||
---|---|---|---|
Product: | WebKit | Reporter: | Jacob Uphoff <jacob_uphoff> |
Component: | SVG | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | ap, cdumez, sabouhallawa, simon.fraser, webkit-bot-watchers-bugzilla, webkit-bug-importer, zimmermann |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=206770 https://bugs.webkit.org/show_bug.cgi?id=224144 |
Description
Jacob Uphoff
2020-01-22 16:12:04 PST
This only seemed to happen once. Looking just a little bit deeper, no, it's happening all the time, just on different test. This is the most recent test run at the moment: https://build.webkit.org/builders/Apple-Catalina-Release-WK2-Tests/builds/2521/steps/layout-test/logs/stdio 07:24:09.704 87914 worker/5 svg/custom/inline-style-overrides-markers-expected.svg crashed, (stderr lines): 07:24:09.704 87914 Unable to shrink memory footprint of process (4322 MB) below the kill thresold (4096 MB). Killed 07:24:09.704 87914 #CRASHED - com.apple.WebKit.WebContent.Development (pid 96223) 07:24:09.706 87856 [52288/52814] svg/custom/inline-style-overrides-markers.svg failed unexpectedly (WebKitTestRunner crashed [pid=95002]) Maybe we can dump a memgraph when this happens? *** Bug 206937 has been marked as a duplicate of this bug. *** > Maybe we can dump a memgraph when this happens?
I don't think that we can take a memgraph after the process gets jetsammed.
If ChromeClient implements didExceedBackgroundResourceLimitWhileInForeground, then we IPC the UI process which can kill the web process if it wants to. So in WTR, we could register this handler (avoiding the instant kill in webcontent), and log something which triggers webkitpy to take a memgraph. Since this jetsam was reproducible by running Web SQL tests, and those tests were being run on the same worker as the blamed SVG tests, I skipped storage/websql tests for iOS and macOS WK2 with https://trac.webkit.org/changeset/255783/webkit |