Snapshot comparison identifies resource growth by recording application state at defined points and comparing the results. For long-running desktop applications, use extended sessions and strict limits because users may notice degradation only after hours of use. section 7.4.1
A practical workflow is:
- Establish a startup baseline, then capture snapshots after one and four hours of representative use. section 7.4.1
- Compare growth against an explicit resource budget and correlate unexplained increases with user actions. section 7.4.1
- Repeat the workflow after remediation to verify that resources are released before the next operation. section 7.4.1
200-image export
An export begins at 180MB and reaches 2.1GB after 150 images, exceeding the 400MB budget. Snapshot evidence shows undo history retaining original images; clearing that history stabilizes usage near 250MB. section 7.4.1



