Quote:
Originally Posted by quisvir
sengian:
I've been able to reproduce the problem, but I'm afraid I've some bad news. After some hours of testing, I've come to the conclusion that it's probably the reader running out of memory. I ruled out PRS+ by uninstalling it, and ruled out Calibre + plugin by changing the cache file manually. But even then, disconnecting from usb after making the changes crashed the reader. I did put 4328 epubs on the SD, so I may have been pushing the device a bit further than you did. And it's likely that the limit is lower when PRS+ is loaded than without it, simply because less memory is available. This could explain why in your case it only crashed with PRS+ loaded. In all, it seems this is a problem that can be avoided, but not fixed.
PS: you can enable logging by putting user.config in /Beta folder on IM. The only line needed is the one that changes defaultLogLevel; you can comment out or remove all the others.
|
This is indeed a bad new. There is no way to handle memory better or to add a swap, optimisation, etc?
I don't know how memory is allocated so I am wondering about it.
Otherwise could it be possible to make a switch ie in PRS+ add an option so that read book are considered unread and read unread. The rationale behind this is that for large book collections the number of book in the list to read is small so that wouldn' t normally be a problem for the reader to handle it.
I can already do this using the read collection, but it would be a nicer and cleaner if a switch was available.
Thanks for PS.