Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Bug: huge memory leak (total red flag)

Abierto
  • ¿Algo no está bien?
#449 1 comentario 1 reacción 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
50/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
android, kotlin
Área
mobile-dev, performance

Línea de trabajo

Reproduce by setting the app as default launcher and monitoring memory via Android Profiler. Look for leaked Activities, Views, or Drawables in launcher-related components. Check for context leaks, uncached bitmaps, or listeners not being removed. Use heap dumps to identify retained objects and trace them to source files in the Kotlin codebase.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug needs triage
Checklist
  • I can reproduce the bug with the latest version given here.
  • I made sure that there are no existing issues - open or closed - to which I could contribute my information.
  • I made sure that there are no existing discussions - open or closed - to which I could contribute my information.
  • I have read the FAQs inside the app (Menu -> About -> FAQs) and my problem isn't listed.
  • I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
  • This issue contains only one bug.
  • I have read and understood the contribution guidelines.
Affected app version

1.10.0

Affected Android/Custom ROM version

Android 16 / One UI

Affected device model

S23

How did you install the app?

GitHub releases

Steps to reproduce the bug
  1. set as default launcher
Expected behavior

for such a minimalist, not many features, and still buggy on widget resizing. this launcher took 250MB of RAM Usage and can go up to 400MB, this is wild!

Actual behavior

you can monitor this through settings > developer options > running devices > cached baclground process

Screenshots/Screen recordings
Image
Additional information
Lenguaje dominante
Kotlin
Estrellas
703
Forks
85
Merge medio
2 d 22 h
PR fusionados (30 d)
10

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de FossifyOrg/Launcher

Todos los issues de FossifyOrg/Launcher

Issues similares

Más issues de Kotlin

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.