Safari and WkWebView Memory Limit Causing App Interruptions

Question

Created Oct ’24

Replies 1

Boosts 0

Participants 1

I'm working on a rather complex web application that includes 3D terrain, 2D mapping, and SVG animations. Both Safari and the Swift app I've built using WkWebKit reload the page after some period of time. Safari pops up a small text block that says:

This webpage was reloaded because it was using significant memory.

Yes. That's true. It's also true that the M1 Max Mac was in now way experiencing issues, nor were any of the other web pages running in other tabs or windows.

The memory limit is simply too low for modern web apps. So far I've not found any way to adjust the parameters in Safari or WkWebView.

Apple, help a brother out. It's not 1997 anymore. Web apps are big. And resetting them at some arbitrary point causes more problems that is solves.

Anyone have any suggestions? Quinn, any way (other than casting a stone into the one-way abyss of Radar) of getting help from the big A here?

Boost

Answer 1

openflight OP

1w

Seriously, crickets? Surely someone else on this forum has experienced this.

Another small issue: in the WkWebKit delegate the only thing we get back when the underlying webKit process dies is the webViewWebContentProcessDidTerminate call. No reason for the termination is given. Webkit has the reason code in the webContentProcessDidTerminateWithReason callback. Any chance that could be exposed in WkWebView? It would be nice to know why the process terminated.

0