This is what I think is the relevant section of the log file going by what it says is going on at that point. Also, it's the only point where there is any gaps at all in what I'm guessing is a time code of some kind (the [114.07] or whatever at the start of some lines). After the end point of this there was no freeze, and the freeze happens after it gets the list of books on the device.
Thanks for the log! I'm a bit unsure how the plugin could freeze Calibre itself since the backup runs in background job, and I don't see any smoking guns in the log, but it would be interesting to know how big the files ".kobo/KoboReader.sqlite" and ".kobo/BookReader.sqlite" are on your device. I'm also wondering if using the "Database → Compress the device database" menu option of the plugin makes any difference.
Thanks for the log! I'm a bit unsure how the plugin could freeze Calibre itself since the backup runs in background job, and I don't see any smoking guns in the log, but it would be interesting to know how big the files ".kobo/KoboReader.sqlite" and ".kobo/BookReader.sqlite" are on your device. I'm also wondering if using the "Database → Compress the device database" menu option of the plugin makes any difference.
KoboReader is 632,155 KB
BookReader is 527,193 KB
Also, I just noticed that the freeze happens IMMEDIATELY after the 'queuing books for...' scroll thing ends where it's getting the list of books or whatever.
After running the compress database tool, KoboReader is 604,725 KB.
davidfor said "BookReader.sqlite is largely used for some of the information related to Kobo Plus and library borrowing. I understand it gets used for other things, but, I don't know what they are. From my experience, it should be fairly small. I would only expect a large size like that if you are borrowing books from Kobo Plus...."
Based on that thread, I'll ask what the time stamp of your BookReader.sqlite file is and if you also have files like BookReader.sqlite-shm and BookReader.sqlite-wal?