That suggests there was a problem. Did you enable logging for this? If so please send that log file to us in a
Support Ticket so we can see what is going on in the background and investigate. You can access the 'Logs' folder with the log file by clicking 'File --> Open User Data Folder' in the main PokerTracker 4 window and the file we need is the text file called 'PokerTracker4' or 'PokerTracker4.log' that is in that folder but if you have since restarted PokerTracker 4 the logs will be in the 'Archive' folder. There is a 10MB limit for attachments so if the relevant log file is larger than that please
zip/compress the log file beforehand. If logging wasn't enabled then please enable it:
1 Start PokerTracker 4.
2. Click "Configure -> Options" and if "Logging Enabled" doesn't have a check mark, click it such that it does.
3. Restart PokerTracker 4.
Now logging will be enabled everytime you start PokerTracker 4. Next time you have an issue you can then send the current log file to us although to avoid waiting you can just let the cache rebuild/restore run for a bit before cancelling it and sending the log and we can check to see if there is anything unusual. Also if this isn't a database specific issue but is a problem with a custom statistic, which I mentioned could be possible, then you may be able to reproduce this issue with one of your smaller databases.