NookGardener wrote:@ deesy58
IMO these are two different issues.
1) Reader Freezes (doesn't do anything, won't let you change font, etc.) is an app issue. The Reader is always running in the background. And we don't really "exit" books, we just move on to the next one. After a certain number of pages, the app just gets stuck. Do you have My App Manager? If you do, I would be curious to know if "Killing the Reader" would allow you to get reopen the book without issue (or having to power off.)
2) Pages getting stuck/not forwarding --- As geertm explained, this is a known issue. FYI, it occurs on Overdrive for Android as well (the library app) so it isn't B&N specific. And the solution (changing the font size to get past the offending page) is the same. Which leads me to think that this is more epub specific. There's different size screens/devices, different fonts, different font sizes, and different margins. You might want to send Alex a PM with the book title you were reading and all the other info so someone at B&N could see if they can replicate the issue.
You make very good points. My thoughts:
1.) When the reader freezes, the device will not respond to any screen touches at all as long as the frozen page is still being displayed. Pressing the "n" key will take me to the main menu that allows me to access the Home page, or to access the Library, but if I try to reenter the book at all, I am taken back to the still-frozen page. IMO, this is, as you believe, an application problem.
2.) It's difficult to imagine that this is an EPUB issue. Unless, of course, it is the Standard, itself, that is causing the problems. It appears to occur randomly, on unpredictable pages in unpredictable e-books. Could it be related to the way that pagination is handled in the EPUB format? Even if it was an EPUB issue, wouldn't you expect a well-designed reader app to respond in a different manner than simply freezing on the page? That's a pretty drastic response to a simple matter of determining the correct page number.
What are the chances that most of the EPUB reader apps are written by the same developer or are based on the same technology? If they are, then a simple thing like an unanticipated anomaly in the EPUB file might make the software "crash," which is certainly what appears to be happening. Once I have rebooted the NOOK, I can no longer reproduce the error in that e-book, so reporting it to B&N would be, IMO, not particularly helpful to them.
Because I frequently leave my NOOK powered on for extended periods, what are the chances that the problem is related to a "memory leak" or similar phenomenon? With no hard drive, a NOOK OS can't "thrash," so what will it do if it runs out of available memory? As you have pointed out, "we don't really "exit" books, we just move on to the next one." That tells me that the "reader" app is running constantly, even between books. So if the reader app is not releasing memory back to the OS, might it run out of memory after a certain number of pages?
Just a thought. I don't really know, but I am curious as to why developers have not tracked down this problem and, at least, identified it to users until such time as it can be rectified. 
