shutdown delays #9668

1. 
   rebroad commented at 0:18 am on February 2, 2017: contributor

   There are a number of areas where bitcoin{d,-qt} is slow in dealing with shutdown requests.

   • getaddrinfo (for the -externalip settings) can take over 25s to return when the DNS entry cannot be found. This causes init.cpp to wait until this has finished, even if shutdown is requested during.
   • ActivateBestChain() currently uses ConnectBlock() which can take >30s per block, and does not respond to shutdown requests while looping through the txs in a block.
   • LoadBlockIndex() although only run at start-up, there are still cases where we may want to shutdown bitcoin (e.g. power-failure) so again it could be more responsive here.
2. jonasschnelli added the label Feature on Feb 2, 2017
3. 
   jonasschnelli commented at 7:22 am on February 2, 2017: contributor

   Yes. We could optimise the shutdown blocking.
4. 
   rebroad commented at 7:16 am on February 7, 2017: contributor

   4a69ae96139eda1ca321b73a9b935e982655dbba is my attempt to rectify the 2nd example.
5. 
   MarcoFalke commented at 6:20 pm on June 19, 2021: member

   Are these still issues on current master?
6. MarcoFalke closed this on May 4, 2022

   ---

7. DrahtBot locked this on May 4, 2023

Contributors
rebroad jonasschnelli MarcoFalke

Labels
Feature