Bug 240397
| Summary: | Enforce foreground WebContent memory limit on macOS | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Ben Nham <nham> |
| Component: | WebKit Process Model | Assignee: | Ben Nham <nham> |
| Status: | RESOLVED FIXED | ||
| Severity: | Normal | CC: | nham, webkit-bug-importer |
| Priority: | P2 | Keywords: | InRadar |
| Version: | Safari 15 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Ben Nham
We removed the foreground memory limit for WebContent in r272046. HoSomBut based on certain bug reports that we've seen, it seems like we need soto restore some limit to prevent bad user outcomes when a misbehaving process has runaway memory usage.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ben Nham
Based on the message above, it looks like the new bug creation tool doesn't handle backspace correctly. A more coherent summary of the bug appears in the commit message.
Radar WebKit Bug Importer
<rdar://problem/93265374>
Chris Dumez
(In reply to Ben Nham from comment #1)
> Based on the message above, it looks like the new bug creation tool doesn't
> handle backspace correctly. A more coherent summary of the bug appears in
> the commit message.
"HoSomBut" -> "Awesome but"? :)
Ben Nham
Pull request: https://github.com/WebKit/WebKit/pull/618
EWS
Committed r294181 (250548@main): <https://commits.webkit.org/250548@main>
Reviewed commits have been landed. Closing PR #618 and removing active labels.