macOS: crash (EXC_BAD_ACCESS) in queued QtNetwork event after network change on DarkWake
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
Línea de trabajo
Start by reviewing the supplied crash stacks and unified log timeline, then trace the QtNetwork event handling and request cancellation paths triggered by a network change during DarkWake. The report identifies no source files or tests, so locating the relevant code will require familiarity with the client and Qt event handling. Done means the client survives the reported network change, reconnects, and resumes syncing.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Pre-submission Checks
- I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
- I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.
Describe the bug
The client crashes reproducibly ~150-250 ms after macOS reports a network change during a DarkWake (Power Nap / maintenance wake). Three crashes (2 Breakpad minidumps, 1 macOS .ips) show the identical faulting location:
QtCore +0xde958 <- EXC_BAD_ACCESS / KERN_INVALID_ADDRESS (0x427, 0x106, 0xac)
QtNetwork +0xb9274
QtCore QObject::event
QtWidgets QApplication::notify
QtCore QCoreApplicationPrivate::sendPostedEvents
libqcocoa / CFRunLoop / NSApplication event loop
The varying small fault addresses suggest a queued (posted) event delivered to a network object that has already been destroyed, likely when in-flight requests are aborted on interface change.
Timeline from unified log (2026-10-27):
07:18:08.915 powerd: DarkWake from Deep Idle
07:18:09.244 configd: DHCP en4/en5/en6/bridge0 status = 'network changed'
07:18:09.410 owncloud crash, crash reporter launched
12:59:00.590 powerd: DarkWake from Deep Idle (rtc/Maintenance)
12:59:00.847 configd: 'network changed'
12:59:01.081 owncloud crash
The 2026-10-21 crash (.ips) has the same stack and occurred 207 s after wake.
Expected behavior
The client should survive a network interface change during a macOS DarkWake (Power Nap / maintenance wake). In-flight requests may be aborted, but the client should keep running, reconnect once the network is available again, and resume syncing without user intervention.
Steps to reproduce the issue
Let the Mac sleep with the client running and syncing; crash happens on a background wake / network interface change.
Screenshots
No response
Logs
No response
Client version number
Client: 7.1.1.19543 (Qt 6.8.3), macOS arm64, build 26A434
Desktop environment (Linux only)
No response
Client package version and origin (Linux only)
No response
Installation path (Windows only)
No response
Server information
Server: oCIS, 18 spaces synced, VFS off
Additional context
Two Breakpad minidumps of the same crash (2026-10-27 07:18 and 12:59) are available. As they contain process memory, I can provide them privately on request.
- Lenguaje dominante
- C++
- Estrellas
- 1.5k
- Forks
- 695
- Merge medio
- 8 d 7 h
- PR fusionados (30 d)
- 6
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de owncloud/client
-
Add Ubuntu 26.04 LTS packagesAbierto
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
Account removal silently keeps the local sync folder, so re-adding creates ownCloud (2), (3), …Posiblemente ocupada @Eiji-Kondo la tomó hace 8 días. Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 25/100
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
Overlay icons show "sync" instead of the warning (yellow) or error (red) icon for sync errors.Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
Los mantenedores suelen responder en 1 día
Todos los issues de owncloud/client
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
HarperFast/rocksdb-js#1131 ·
Los mantenedores suelen responder en 1 día
-
area/daemon bug good first issue platform/linux priority/p2
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
ToshiNamura/Deimos#5 ·
-
needs-format
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Niko1221/Strata#6251 · 1 comentario ·
Los mantenedores suelen responder en 5 días
-
[Bug]: NP 管理器文件编辑器里删除键无效Abiertobug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
metasequoiaime/msime#11666 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
patrick-hudson/put.gd-desktop#1679 · 1 comentario ·
Los mantenedores suelen responder en 1 día