Booted up v20, it's downloading the last few days worth of blocks.  Froze up a few times but not for too long.  I'm watching memory pressure on the activity monitor, it's all green, even when Bitcoin Core Freezes.  The CPU tab shows Bitcoin Core not responding during a freeze but no memory use spike.

Thanks!  I'm beginning to think you're right.  May be time to upgrade.    Copied my backup to a clean 2tb drive, booted up Bitcoin Core and it's at the Rescanning stage.

>No, -reindex parameter forces Bitcoin Core to rebuild the chainstate and blockchain index from the blocks which have been already downloaded.

Thanks!

Edit:   Could hard drive fragmentation have something to do with constant freezing?  I'm copying my backup blockchain file to a fresh new 2tb drive.  I'll try booting from that.

Nope, didn't seem to help.  I cleared out 50GB free space, rebooted Bitcoin Core.  Once it was up, it picked up where it left off on the -reindex but as soon as I click a button or move the mouse it goes back to the spinning pinwheel for five minutes or so then the "Last Block Time" jumps by an hour or two then back to the freeze and pinwheel.  

Edit:  Does this -reindex require constant internet?  I'm in a hotel with poor wi-fi, cuts out for a few minutes a few times a day.

Thanks!  I have a large folder of books I can take off the laptop and archive.  I'll free up the space and see if it helps.   I do tend to keep the laptop full.

Bitcoin Client Software and Version Number: Upgrading to Bitcoin Core v.20 from v.15
Operating System: Mac OS 10.14.1
System Hardware Specs:  MacBook Air  8GB RAM, 12GB free on machine, 1.5TB free on Seagate media drive.

Description of Problem: Upgraded Bitcoin core to v.20 last night.  After I got it up and running, the performance started to lag badly.  I couldn't even move the cursor or click a button without the program freezing for 30 sec to five minutes.  All I see is the spinning pinwheel.   This frequent freezing has happened in earlier versions but never this badly. I ran -reindex from the terminal window and I noticed some error messages (cut and paste below) popping up as the reindexing happens.  Freezes for 30 sec to five minutes like it’s choking a block that’s too big.  Progress increase per hour will be in the 10% range then drop to .08-.10% for a while.  Rebooting doesn't seem to help.  Terminal messages only appear for the longer freezes, not the shorter ones. 

Sent some satoshi to another wallet as a test and after a five minute freeze when clicking the send button, they finally left my wallet balance.  With $1.50 fee, they still haven't arrived after 12 hours.  I double clicked on the transaction to see the details, and after three minutes of the pinwheel the details opened.  Can't find the transaction hash on blockchain.info so thinking it's still in the mempool.

Any Related Addresses: n/a Not really worried about the transaction, it will pop out eventually.  $1.50 fee/246 bytes.  Thinking it wasn't broadcast due to the crashing.

Any Related Transaction IDs: n/a
Screenshot of the problem: n/a

Log Files from the Bitcoin Client:  (cut and paste from Terminal window, let me know if there's anything else you need.

2020-06-06 06:13:26.194 Bitcoin-Qt[583:14140] IMKClient Stall detected, *please Report* your user scenario attaching a spindump (or sysdiagnose) that captures the problem - (imkxpc_windowLevelWithReply:) block performed very slowly (1.77 secs).
2020-06-06 08:02:05.250 Bitcoin-Qt[583:14140] IMKClient Stall detected, *please Report* your user scenario attaching a spindump (or sysdiagnose) that captures the problem - (imkxpc_attributesForCharacterIndex:reply:) block performed very slowly (167.51 secs).
2020-06-06 08:02:05.250 Bitcoin-Qt[583:14140] IMKClient Stall detected, *please Report* your user scenario attaching a spindump (or sysdiagnose) that captures the problem - (imkxpc_windowLevelWithReply:) block performed very slowly (165.51 secs).

Great, thank you both.  Much appreciated.

I tried the -addnode command in Terminal but I get the following error:

/Applications/Bitcoin-Qt.app/Contents/MacOS/Bitcoin-Qt -addnode=<50.155.31.101:8333>

-bash: syntax error near unexpected token `newline'

With the blockchain file updated on the other computer it seems to be opening consistently now.

Great!  Thank you so much for your help.  And everyone else too!

Thanks for that analysis and info.  Much appreciated!

-connect=<ip> Connect only to the specified node(s)

Do I use the above to change the node?

Here's a copy of the debug log for the last startup of the program.   After opening it on my roommate's MacBook pro last night I let the blockchain update then closed the program.  It's after work today and I'm back on my computer.  This time Bitcoin core opened very quickly just like it used to.   Perhaps the issue lies with how my computer is updating the blockchain and closing files?  Thanks to everyone for the assistance!

from the debug file:
-----------------

2017-01-06 23:47:03 Bitcoin version v0.13.2
2017-01-06 23:47:03 InitParameterInteraction: parameter interaction: -whitelistforcerelay=1 -> setting -whitelistrelay=1
2017-01-06 23:47:04 Default data directory /Users/ianmelnicsak/Library/Application Support/Bitcoin
2017-01-06 23:47:04 Using data directory /Volumes/SEAGATE 2TB/untitled folder 2
2017-01-06 23:47:04 Using config file /Volumes/SEAGATE 2TB/untitled folder 2/bitcoin.conf
2017-01-06 23:47:04 Using at most 125 connections (2560 file descriptors available)
2017-01-06 23:47:04 Using 2 threads for script verification
2017-01-06 23:47:04 Using BerkeleyDB version Berkeley DB 4.8.30: (April  9, 2010)
2017-01-06 23:47:04 Using wallet wallet.dat
2017-01-06 23:47:04 scheduler thread start
2017-01-06 23:47:04 init message: Verifying wallet...
2017-01-06 23:47:04 CDBEnv::Open: LogDir=/Volumes/SEAGATE 2TB/untitled folder 2/database ErrorFile=/Volumes/SEAGATE 2TB/untitled folder 2/db.log
2017-01-06 23:47:04 Bound to [::]:8333
2017-01-06 23:47:04 Bound to 0.0.0.0:8333
2017-01-06 23:47:04 Cache configuration:
2017-01-06 23:47:04 * Using 2.0MiB for block index database
2017-01-06 23:47:04 * Using 8.0MiB for chain state database
2017-01-06 23:47:04 * Using 290.0MiB for in-memory UTXO set
2017-01-06 23:47:04 init message: Loading block index...
2017-01-06 23:47:04 Opening LevelDB in /Volumes/SEAGATE 2TB/untitled folder 2/blocks/index
2017-01-06 23:47:05 Opened LevelDB successfully
2017-01-06 23:47:05 Using obfuscation key for /Volumes/SEAGATE 2TB/untitled folder 2/blocks/index: 0000000000000000
2017-01-06 23:47:05 Opening LevelDB in /Volumes/SEAGATE 2TB/untitled folder 2/chainstate
2017-01-06 23:47:06 Opened LevelDB successfully
2017-01-06 23:47:06 Using obfuscation key for /Volumes/SEAGATE 2TB/untitled folder 2/chainstate: 0000000000000000
2017-01-06 23:47:10 LoadBlockIndexDB: last block file = 731
2017-01-06 23:47:10 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=53, size=52231321, heights=446361...446915, time=2017-01-03...2017-01-06)
2017-01-06 23:47:10 Checking all blk files are present...
2017-01-06 23:47:11 LoadBlockIndexDB: transaction index disabled
2017-01-06 23:47:11 LoadBlockIndexDB: hashBestChain=00000000000000000368447994eaab272102ae239197d12292e387bd3af3d95c height=446820 date=2017-01-06 03:39:22 progress=0.999677
2017-01-06 23:47:11 init message: Rewinding blocks...
2017-01-06 23:47:13 init message: Verifying blocks...
2017-01-06 23:47:13 Verifying last 6 blocks at level 3
2017-01-06 23:47:13 [0%]...[16%]...[33%]...[50%]...[66%]...[83%]...[99%]...[DONE].
2017-01-06 23:47:38 No coin database inconsistencies in last 7 blocks (16907 transactions)
2017-01-06 23:47:38  block index           33762ms
2017-01-06 23:47:38 init message: Loading wallet...
2017-01-06 23:47:38 nFileVersion = 130200
2017-01-06 23:47:38 Keys: 0 plaintext, 320 encrypted, 320 w/ metadata, 320 total
2017-01-06 23:47:38  wallet                  296ms
2017-01-06 23:47:38 mapBlockIndex.size() = 446980
2017-01-06 23:47:38 nBestHeight = 446820
2017-01-06 23:47:38 setKeyPool.size() = 99
2017-01-06 23:47:38 mapWallet.size() = 179
2017-01-06 23:47:38 mapAddressBook.size() = 140
2017-01-06 23:47:38 init message: Loading addresses...
2017-01-06 23:47:38 torcontrol thread start
2017-01-06 23:47:38 Loaded 62567 addresses from peers.dat  333ms
2017-01-06 23:47:38 init message: Loading banlist...
2017-01-06 23:47:39 init message: Starting network threads...
2017-01-06 23:47:39 dnsseed thread start
2017-01-06 23:47:39 upnp thread start
2017-01-06 23:47:39 net thread start
2017-01-06 23:47:39 init message: Done loading
2017-01-06 23:47:39 addcon thread start
2017-01-06 23:47:39 opencon thread start
2017-01-06 23:47:39 msghand thread start
2017-01-06 23:47:39 GUI: Platform customization: "macosx"
2017-01-06 23:47:39 GUI: PaymentServer::LoadRootCAs: Loaded  169  root certificates
2017-01-06 23:47:39 GUI: QObject::connect: No such slot RPCConsole::test() in qt/rpcconsole.cpp:668
2017-01-06 23:47:39 GUI: QObject::connect:  (receiver name: 'RPCConsole')
2017-01-06 23:47:39 ProcessMessages: advertising address 72.48.196.142:8333
2017-01-06 23:47:39 receive version message: /Satoshi:0.13.1/: version 70014, blocks=446963, us=72.48.196.142:54757, peer=1
2017-01-06 23:47:39 AdvertiseLocal: advertising address 72.48.196.142:8333
2017-01-06 23:47:41 UPnP: ExternalIPAddress = 72.48.196.142
2017-01-06 23:47:41 AddLocal(72.48.196.142:8333,3)
2017-01-06 23:47:41 UPnP Port Mapping successful.
2017-01-06 23:47:45 connect() to 87.120.37.230:8333 failed after select(): Connection refused (61)
2017-01-06 23:47:46 connect() to [2002:422a:8362::d4a8:4f6d:3696:6781]:8333 failed: No route to host (65)
2017-01-06 23:47:50 Loading addresses from DNS seeds (could take a while)
2017-01-06 23:47:51 129 addresses found from DNS seeds
2017-01-06 23:47:51 dnsseed thread exit

I just tried it on his MacBook Pro 2.7ghz with 8gb RAM.  It crashed just as the intro screen said "Done Loading" but opened after a minute or so. 

It wasn't doing this on my MacBook Air with 4GB RAM just three weeks ago, it's a recent development.

Thank you for that info.  I had a feeling that may be the case, 4GB RAM and a 1.3ghz processor.  Seems to go a little faster if I have all other programs closed when I try to load Bitcoin Core.  I'm testing this idea right now on my roommate's MacBook Pro with a 2.7ghz processor and 8GB RAM.

Hi-

Bitcoin Core recently started taking a long time to load.  Usually just takes a few minutes but lately it's taking 5-15 minutes.  Started about three weeks ago.  I've sometimes had to do a force quit and restart the loading process. 

MacBook Air running 10.12.1
bitcoin files are on a 2tb external drive.  this drive is only for bitcoin stuff, no other files or data.
running Bitcoin Core 0.13.1, updated to 0.13.2 but having the same problem.
wallet.dat file backed up to several other drives.

I double click on the Bitcoin Core application and the usual intro window pops up with the following info along the bottom:

Rewinding Blocks
Loading Blocks 1%
Loading Blocks 13%
Loading Blocks 33%
Loading Blocks 66%
Loading Blocks 83%
Loading Blocks 99%
Starting Network Threads
Done Loading

After it hits "Done Loading" it freezes up for anywhere between 5-15 minutes before opening.  The window continues to say "Done Loading" but the cursor turns into the little rainbow ball and if I click on the Bitcoin Core icon in the dock I have the option to force quit. 

If I just leave it alone eventually whatever is wrong will work itself out (5-15 minutes or so) and the program will open normally and is fully functional.  I have tried running the -rescan command but that didn't seem to help at all. 

I've tried to google this problem but I can't seem to find any posts that have a similar issue.  Has anyone else run into this?

Thanks