Skip to content

Commit 5aa4956

Browse files
furszyfanquake
authored andcommitted
gui: crash fix, disconnect numBlocksChanged() signal during shutdown
The crash stems from the order of the shutdown procedure: We first unset the client model, then destroy the wallet controller—but we leave the internal wallet models ('m_wallets') untouched for a brief period. As a result, there’s a point in time where views still have connected signals and access to wallet models that are not connected to any wallet controller. Now.. since the clientModel is only replaced with nullptr locally and not destroyed yet, signals like numBlocksChanged can still emit. Thus, when wallet views receive them, they see a non-null wallet model ptr, and proceed to call backend functions from a model that is being torn down. As the shutdown procedure begins by unsetting clientModel from all views. It’s safe to ignore events when clientModel is nullptr. Github-Pull: gui#864 Rebased-From: 71656bd
1 parent 3665310 commit 5aa4956

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/qt/sendcoinsdialog.cpp

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -851,6 +851,10 @@ void SendCoinsDialog::updateCoinControlState()
851851
}
852852

853853
void SendCoinsDialog::updateNumberOfBlocks(int count, const QDateTime& blockDate, double nVerificationProgress, SyncType synctype, SynchronizationState sync_state) {
854+
// During shutdown, clientModel will be nullptr. Attempting to update views at this point may cause a crash
855+
// due to accessing backend models that might no longer exist.
856+
if (!clientModel) return;
857+
// Process event
854858
if (sync_state == SynchronizationState::POST_INIT) {
855859
updateSmartFeeLabel();
856860
}

0 commit comments

Comments
 (0)