Piye cara memory management ing Android lan carane nyegah leaks?

Question

Accepted Answer

Android apps mlaku kanthi **memory winates** lan bisa dipateni sistem nalika memory pressure. Ngerti memory management — utamane **nyegah memory leaks** (masalah Android sing umum lan serius) — penting kanggo apps sing stabil lan performan.

## Basis memory Android

```text
→ Apps have a LIMITED heap; the system can KILL background apps to reclaim memory
→ Garbage collection reclaims unreachable objects — but GC pauses can cause jank, and
  objects that STAY reachable (leaks) are never collected
→ Low-memory devices are common (Android's range) → memory efficiency matters
```

## Memory leaks — masalah umum

```text
A LEAK = an object that's no longer needed but is still REFERENCED (so GC can't free it).
Classic Android leaks:
  ✗ Holding an ACTIVITY/Context reference beyond its lifecycle:
    - a static field or singleton holding an Activity/Context
    - a long-lived listener/callback capturing an Activity
    - an inner class / non-cancelled coroutine / handler holding the Activity
  → the Activity can't be GC'd after it's destroyed → its whole view tree leaks (big!)
```

## Nyegah leaks

```text
✓ Don't hold Activity/Context in static fields or long-lived objects (use applicationContext
  where a long-lived context is needed)
✓ UNREGISTER listeners/observers; CANCEL coroutines (lifecycle scopes auto-cancel)
✓ Use LIFECYCLE-AWARE components (ViewModel, lifecycleScope, LiveData) — they clean up
✓ Be careful with inner classes/handlers (use weak references or static + WeakReference)
✓ DETECT with LeakCanary (flags leaks in development); profile memory in Android Studio
```

## Kahanane iki

Ngerti Android memory management lan nyegah leaks iku pengetahuan level senior penting amarga **memory leaks iku masalah Android sing umum lan serius** sing ngurusi performa lan nyebabake crashes, lan lingkungan Android kanthi memory terbatas lan app-killing sistem nggawe memory efficiency dadi penting, dadi iku berharga kanggo ngbangun apps sing stabil.

Android apps mlaku kanthi **memory winates** lan sistem bisa mateni apps nalika memory pressure, saengga garbage collection bakal ngreklaim objects sing ora bisa dijangkau nanging ora bisa mbusak objects sing isih ana reference (leaks) — nggawe memory management dadi penting, utamane amarga akeh Android devices kanthi memory rendah. **Memory leaks iku masalah Android sing paling umum lan dampak besar**: object sing ora dibutuhake lagi nanging isih ada reference ora bisa garbage-collected, lan **classic Android leaks nglibatke nyekel Activity/Context references ngluwihi lifecycle-ne** (liwat static fields, singletons, long-lived listeners, inner classes, handlers, utawa coroutines non-cancelled sing nyubit Activity) — sing utamane ala amarga Activity leaks nyeret entire view tree-ne, leaks memory sing gede.

Ngerti pola leaks iki penting amarga sering lan real sources masalah memory lan crashes.

Ngerti **carane nyegah leaks** — ora nyekel Activity/Context ing static utawa long-lived objects (nggunakake applicationContext yen pantes), unregistering listeners lan cancelling coroutines (lifecycle scopes auto-cancel), nggunakake **lifecycle-aware components** (ViewModel, lifecycleScope, LiveData sing ngresiki otomatis), ati-ati nganggo inner classes/handlers, lan **detecting leaks nganggo LeakCanary** lan profiling — iku pengetahuan praktis essential kanggo nyegah.

Amarga memory leaks iku masalah Android sing umum lan serius (utamane Activity/Context leaks) lan lingkungan Android kanthi memory terbatas nggawe efficiency penting, lan amarga ngerti memory management lan pola-pola kanggo nyegah leaks (lifecycle-aware components, proper cleanup, detection tools) kudu kanggo apps stabil lan performan, dadi ngerti Android memory management lan leak avoidance iku pengetahuan level senior penting — nyusuturi salah siji masalah Android paling umum lan dampak gede, nunjukkake expertise platform-specific sing dibutuhake kanggo ngbangun apps stabil lan depth sing dikarepake kanggo senior Android roles.