Daily iOS
Performance and debugging

Responding to memory warnings

A photo editing app gets frequent memory warnings and sometimes gets killed. In what order would you track down the cause?

How would an interviewer hear this answer? You'll see whether they'd move on, dig in, or say no, and which sentences would trip you up. Your score doesn't change.
See the short answer

Measure what's taking the memory first with Allocations and the Memory Graph. In a photo app, suspect decoded photo sizes and the cache policy, and fix the peak before you polish the warning handler.

Share a question