15 comments (15 comments)2 reactions (2 reactions)0 assignees (0 assignees)Swift9,877 stars (9,877 stars)368 forks (368 forks)batch import
help wantedrisk
Description
As the usage time increases, the CPU usage of the app also continues to increase.
Contributor guide
- Tech stack
- swift
- Domain
- performanceobservability
- Issue type
- bug
- DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
- 4
- Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
- 1-2 days
- Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
- stale
- ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
- needs investigation
- Prerequisites
- SwiftSwiftUIXcode Instruments
- Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
- 30
- Research direction
- Investigate potential memory leaks or infinite loops causing increasing CPU usage. Use Xcode's Time Profiler to identify hot spots in the app's main loop or background tasks. Focus on SwiftUI view updates or timer based operations that might not be deallocated. Check for strong reference cycles in closures or Combine publishers. The issue lacks specific reproduction steps, so first reproduce by running the app for an extended period and monitoring CPU usage with Activity Monitor.