Thread: Normal for kobo to take forever on "processing content" ?
View Single Post
Old 05-30-2021, 08:14 PM   #102
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Dchiplin View Post
I appreciate the responses.

I don’t honestly think there is an issue with my books. Most of them were on this reader before as well as my “back-up” Koba Aura H2O.

I think it’s a Calibre problem. I am trying again to transfer 10 books and it is maxing my memory (4,500MB) and also high CPU.

Last night the job died after 3 plus hours and the application threw a .net error. I tried to cut and paste the details but whole laptop was unresponsive.

I have run a chkdsk on the Reader and it was ok.

I have also run Library Maintenance (Vacuuming?) in Calibre.

I should also mention that I have a large library -60+ GBs/10K+ items - as I have a lot of cookbooks. But the books I am transferring are just regular small novels.
If calibre behaved like that, it is almost definitely one of your books. An important phrase above is, "Most of them". Meaning, it is probably one of the books that fit into that category that is the problem. But, even easier, is that one of the 10 books you tried to transfer is a culprit. You could simply try sending them one at a time and see what happens. And of course, you can try a different small set of books and see what happens.

But, there are some questions to ask:
  • What format are the books? Are they being converted from other formats to epub before the send?
  • Are you using the built-in KoboTouch driver or the user installed KoboTouchExtended driver?
  • How big are these books?
  • There are two or three jobs run when sending a book to the device. Which one was being run when this happened?
  • Have you tried sending these books to the device before?
  • Are you running any anti-virus or anti-malware that could be trying to "help"?
  • Is there plenty of space on whatever drive the temporary directory is on?
  • Are there any issues getting the list of books from the device? That is, when you plugin the device, does calibre bring back the list of books.
  • What versions are you using? That is version of calibre, the firmware, OS and anything else that might be pertinent.

Apart from that, I would like to see a debug log from calibre. I usually ask people to restart restart calibre in debug mode, connect the device and do whatever the problem is and post the log after closing calibre. That should give hints of what is happening. In this case, it would probably be better to start calibre from the command-line with "calibre-debug -g". That will write output to the command-line window and can be captured from there. Or use:
Code:
calibre-debug -g > debug.log 2>&1
That should write to a file you can see if you need to kill calibre. You might need to supply the path for "calibre-debug" as well. It will depend on your setup.
davidfor is offline   Reply With Quote