diff options
author | furszy <matiasfurszyfer@protonmail.com> | 2023-09-08 10:58:37 -0300 |
---|---|---|
committer | fanquake <fanquake@gmail.com> | 2023-10-03 15:58:41 +0100 |
commit | 64ffa9423197c2dad2f5c5d812e1b17d6b9030f0 (patch) | |
tree | 9450c23c9d070b4dd3d80c603a99c5e0758db4c2 /src/kernel/chainparams.cpp | |
parent | e270f3f8578d933e8f219b3381ac105185b3b707 (diff) |
gui: macOS, do not process dock icon actions during shutdown
As the 'QMenuBar' is created without a parent window in MacOS, the
app crashes when the user presses the shutdown button and, right
after it, triggers any action in the menu bar.
This happens because the QMenuBar is manually deleted in the
BitcoinGUI destructor but the events attached to it children
actions are not disconnected, so QActions events such us the
'QMenu::aboutToShow' could try to access null pointers.
Instead of guarding every single QAction pointer inside the
QMenu::aboutToShow slot, or manually disconnecting all
registered events in the destructor, we can check if a
shutdown was requested and discard the event.
The 'node' field is a ref whose memory is held by the
main application class, so it is safe to use here. Events
are disconnected prior destructing the main application object.
Furthermore, the 'MacDockIconHandler::dockIconClicked' signal
can make the app crash during shutdown for the very same
reason. The 'show()' call triggers the 'QApplication::focusWindowChanged'
event, which is connected to the 'minimize_action' QAction,
which is also part of the app menu bar, which could no longer exist.
Github-Pull: gui#751
Rebased-From: e14cc8fc69cb3e3a98076fbb23a94eba7873368a
Diffstat (limited to 'src/kernel/chainparams.cpp')
0 files changed, 0 insertions, 0 deletions