You've just hit a special category of bug, viewing a post that straight up consumes all available memory and forces the OS to terminate the app. Here's another such example.

This kind of crash is the worst because there's no way Crashlytics, or even Apple, can generate a meaningful bug report and there's really no way for us to avoid it. We just have to live with it.

Fun graphs:

Just a UIWebView rending the desktop version:

You'll notice that the memory maxes out at half of the available RAM.

Throw in a the fact we're scaling the image, holding multiple web views, keeping more web view layers in memory than we probably should, etc, the real app looks more like this when displaying the image:

This second graph hits 80% memory usage, just in the app, so it's no wonder that the OS would kill it.

You've just hit a special category of bug, viewing a post that straight up consumes all available memory and forces the OS to terminate the app. Here's another such example.

This kind of crash is the worst because there's no way Crashlytics, or even Apple, can generate a meaningful bug report and there's really no way for us to avoid it. We just have to live with it.

Fun graphs:

Just a UIWebView rending the desktop version:

You'll notice that the memory maxes out at half of the available RAM.

Throw in a the fact we're scaling the image, holding multiple web views, keeping more web view layers in memory than we probably should, etc, the real app looks more like this when displaying the image:

This second graph hits 80% memory usage, just in the app, so it's no wonder that the OS would kill it.