Quote:
Originally Posted by momoha
I really don’t get it. I did many tests, and at some point the book always crash. Here’s what I tested:
- Without javascript
- Without animations
- With all the CSS sheets empty
- Without the images
- Without the fonts
And I don’t have an iPad air... |
Back in iOS 7, I kept running into a bad kernel memory leak that caused apps to crash en masse if the device had been up and running without a reboot for 30+ days (depending on usage). The problem might still happen in iOS 8. So if you haven't tried shutting the device completely off and booting it back up, try that first.
Short of something like that, I'd be surprised if the problem were caused by a lack of RAM, particularly given that the device that is failing has at least as much RAM as the one that is working.
With that said, if you want to try to experiment with RAM reduction, the iBooks rendering engine (WebKit) always has just a single HTML file in memory at any given point in time, discarding the previous one as it passes a page boundary. Of course, there's also a back/forward cache and various other caches, so that's not precisely true, but either way, the less you put in a given HTML file, the less should be in memory at any given moment, and those caches are thrown away if you run out of memory, so they shouldn't be a problem.
I mean, I suppose it is possible that iBooks might be doing something silly like extracting the entire Zip archive in RAM, but I doubt it.
A couple more questions:
1. Does it fail reliably when you advance to any particular page? Or away from any particular page?
2. Could you paste in the crash log file? (It might not be of any help, but then again, it might.)