View Single Post
Old 10-30-2011, 12:16 AM   #29
David58117
Groupie
David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.David58117 ought to be getting tired of karma fortunes by now.
 
Posts: 165
Karma: 1020558
Join Date: Oct 2011
Device: Sony T1, K4NT (To Wife), Nook ST, NSTG
Quote:
Originally Posted by pe1dnn View Post
If and how often it occurs depends on the device. The problem occurs frequently on some (several times in one evening) and seldom (once a week) or even never on others (or only once a month or once a year...).

My PRS-T1 I have seems to do it seldom, in the 1 1/2 weeks I have it, it happened only twice. Swiping is almost consistently okay, almost. But 2 occurrences is not enough too tell the actual frequency, maybe it will not crash for a whole week or maybe it is already the next page turn I will do.

From the reports so far it seems some have it more often than others which of course leads to a different perception of the severity of the problem and even denial by those who had the luck not to encounter the problem (up to now...).

My guess is the problem is a timing issue which are the type of bugs in realtime systems (such as a device driver) which are very hard to track down because it is not repeatable but depends on sheer luck of having an event just at the wrong time. Like Russian Roulette with a revolver with 1000 slots. 999 do not have a problem but the one shot does. And some have more bullets and others have none, making it all very unpredictable.

What makes this worse is when a Sony designer/tester adds debugging code to track down the bug, the extra code may well prevent the bug from happening at all. So it is not easy to find the cause. Maybe it cannot be found by debugging/testing but only by code review, analysing every possible path through the code.

But what is apparent is that the bug exists and is bugging the user off guard at unexpected times. It is just not reliable, you cannot trust the next swipe to succeed.

I hope this was clear to you.
Clear for me? Hm..I think you've come in late to the conversation and missed a few steps..

Some reports make it sound like a memory leak, and on a few threads back some posters noticed certain behaviors of readers having a problem being in common...such as using touchscreen primarily, reading straight for hours at a time without switching screens or putting it to sleep...stuff like that, although some crashes/freezes appear to just be out of the blue. I've never had one while reading a book or out of the blue, so in an attempt to see if it is the behavior causing a crash, the past two weeks I've used only touch screen. Nothing yet so far. I suppose next I'll use only touchscreen and won't switch out of a book when I stop reading...maybe the action of switching screens clears the memory - I don't know, but worth a test I suppose.
David58117 is offline   Reply With Quote