macOS: crash (EXC_BAD_ACCESS) in queued QtNetwork event after network change on DarkWake

Aperta
#12,674 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
cpp
Ambito
desktop

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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

owncloud-crash-ips.zip

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.

Lingua principale
C++
Stelle
1.5k
Fork
695
Merge medio
8g 7h
PR unite (30g)
6

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di owncloud/client

Tutte le issue di owncloud/client

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.