Thread: Glo Glo stalls during scan of reloaded collection ?.
View Single Post
Old 01-15-2015, 06:11 PM   #3
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 leftright View Post
Kobo Glo v3.12. All epubs sideloaded.

I deleted all books in my Glo using the remove function in settings.
I transferred my entire collection from Calibre to Glo, transfer Ok.
I disconnected from PC and the Glo's scan feature started, but it stalled at 80%, I left it for two days and the progress bar didn't move past 80%, pin hole reset was required to restart the Glo, Zero books in it.

I connected Glo to Calibre, Calibre shows that books are in Glo.
I re-deleted all books via settings and proceeded to transfer books from Calibre to Glo piecemeal, after each small transfer I disconnected the Glo letting it scan, then I'd reconnect the Glo to Calibre for another transfer.
It took forever but ALL books were successfully scanned by the Glo.

1). Why would the glo hang during the scan of the entire collection and not during the piecemeal reload and rescan ?.

2). If it does encounter a problem book, why doesn't it skip that book and continue ?.

Suggestion:
If there are problem books that it stalls on, skip them and continue with the loading of subsequent books, then display a fault log at the end.
How many books did you send? As they processed ok in small groups, the issue was probably the bulk lot. I think the maximum I have processed in one go is about 1500. That was after a logout and back in and took a couple of hours. My guess would be that as the number of books gets larger, any inefficiencies in the code get amplified. It's build a list of books and their details, if it needs to search that list as a new book is added, that get slower with each book. And if there are any code problems, such as a small memory leak per book, then when you hit several thousand books, they will build and cause a bigger problem. Remember, these are very low power devices with little RAM. Expecting them to process stuff as quickly and efficiently as your desktop PC is absurd.

And before you say "But they should fix these problems". Of course they should. But, they have to choose which problem to fix first. Do they fix a problem that only affects a small number of people doing an uncommon task (loading thousands of books in one go) that also has a reasonably easy workaround (load them in batches), or a problem that affects a lot of people? They also have to know about the problem. If no-one has reported a bug, they can't fix it.
davidfor is offline   Reply With Quote