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

オープン
#12,674 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
cpp
領域
desktop

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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.

主要言語
C++
スター
1.5k
フォーク
695
平均マージ
8日 7時間
マージ済み PR(30日)
6

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

owncloud/client のほかの issue

owncloud/client の issue をすべて見る

似ている issue

C++ の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。