Thread: Calibre crash / Kobo Libra 2 / MacOS
View Single Post
Old 03-23-2022, 07:44 PM   #6
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 kovidgoyal View Post
And I spoke too soon, the crash is actually caused by parsing of XML or HTML in libxml2 (crashed thread is #106). It might just be the set of books you are sending. One or more of them is causing a crash. So if you can repeat the crash send smaller subsets of the books to isolate which one is the problem. If you can find that I can try to replicate and investigate. And of course try without the extended plugin as well, as that does more things to books when sending them.
That probably is happening in the extended driver. Among other things, it wraps each sentence in the book in a span which is used on the device for the locations in the book.

There was an issue a while ago with the extended driver on Macs. It was triggered by a change made for multi-threading the book changes. I thought it had been fixed, but, maybe it is still triggered under some circumstances.
davidfor is offline   Reply With Quote