245222 2022-09-15 07:30:58 -0700 REGRESSION(250548@main): Early WebProcess exit on 32-bit platforms since memory limit is zero 2022-09-16 00:32:51 -0700 1 1 1 Unclassified WebKit WebCore Misc. WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED https://bugs.webkit.org/show_bug.cgi?id=241012 InRadar P2 Normal --- 1 olivier.blin webkit-unassigned cdumez cgarcia darin loic.yhuel mafm magomez mcatanzaro nham webkit-bug-importer zdobersek oldest_to_newest 1898696 0 olivier.blin 2022-09-15 07:30:58 -0700 In 250548@main, the memory limit in MemoryPressureHandler is set to a least 7 GB for active process. This value is stored in a size_t variable, but this is limited to 4 GB on 32-bit platforms. The memory limit is truncated down to 0, which triggers a WebProcess exit after the first MemoryPressure check. 1898698 1 olivier.blin 2022-09-15 07:32:34 -0700 Pull request: https://github.com/WebKit/WebKit/pull/4381 1898712 2 magomez 2022-09-15 08:56:21 -0700 Folks, this is already being handled in https://bugs.webkit.org/show_bug.cgi?id=241012. The PR for this addresses the value overflow, but what should be done is that WebKitGTK and WPE shouldn't use those values at all. 1898713 3 cdumez 2022-09-15 08:58:40 -0700 (In reply to Miguel Gomez from comment #2) > Folks, this is already being handled in > https://bugs.webkit.org/show_bug.cgi?id=241012. > > The PR for this addresses the value overflow, but what should be done is > that WebKitGTK and WPE shouldn't use those values at all. I think https://github.com/WebKit/WebKit/pull/4381 is valuable no matter what. If you want to disable this handling for WebKitGTK and WPE and fine but that's a separate issue from the overflow handling on 32bit. 1898821 4 ews-feeder 2022-09-15 15:13:50 -0700 Committed 254533@main (b0895ea02d48): <https://commits.webkit.org/254533@main> Reviewed commits have been landed. Closing PR #4381 and removing active labels. 1898822 5 webkit-bug-importer 2022-09-15 15:14:22 -0700 <rdar://problem/99989909> 1898920 6 magomez 2022-09-16 00:32:51 -0700 *** Bug 241012 has been marked as a duplicate of this bug. ***