These changes block a wallet unload until the GUI completes the process of its model loading.
Fix #18362
@ryanofsky Not sure about this PR approach w.r.t. upcoming multiprocessing.
NACK, sorry but I think this is really the wrong approach.
<!--e57a25ab6845829454e8d69fc972939a-->
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
<!--174a7506f384e20aa4161008e828411d-->
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.
Confirmed 81d4a7b7e3d096ef6f7586eb34dfd2653432c504 works and stops the segfaults. Thanks for the fix! Also agree that the simpler, non-blocking fix 838ea490dd2641e746f870182822dcdf060caa89 from #18338 is probably more robust, and less likely to lead to gui hangs or deadlocks if code is changed in the future.
@ryanofsky Not sure about this PR approach w.r.t. upcoming multiprocessing.
Should be no interaction, at least with #10102 all stc/interfaces calls are normal blocking calls that run in the same order, just slower