View Single Post
Old 02-13-2017, 04:53 AM   #11
Josieb1
Grand Sorcerer
Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.Josieb1 ought to be getting tired of karma fortunes by now.
 
Posts: 5,086
Karma: 18051062
Join Date: Nov 2009
Location: UK
Device: Kindle Scribe, Coloursoft, PW SE, Kindle 6, Kobo Libra 2
Quote:
Originally Posted by chaley View Post
The problem seems to be related to iOS memory management, which is why it is so hard to replicate. Free memory is collected periodically, but the period is unpredictable. An app can run out of memory between collections. I mention this because contrary to what I said in your calibre bug report, the fact you are using TXT files might actually be relevant. It will take *much less time to send empty TXT files than to send real books, meaning books will arrive much more quickly meaning that CC will touch the database far more frequently than "normal". If I am right then sending smaller groups and waiting a bit between them might help.

[/URL].
I was using my MAC this time which has 8GB of memory, DH's W10 PC has 12GB, I will install the 64bit calibre on his PC, and later this week I will try again using smaller batches and see what happens. As this problem did affect another person it will be interesting to see if the problem is fixed for them.

I don't mind the crashing tbh if only the app wouldn't wipe itself clean when it does.
Josieb1 is offline   Reply With Quote