View Single Post
Old 12-17-2009, 10:36 PM   #110
starrigger
Jeffrey A. Carver
starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.starrigger ought to be getting tired of karma fortunes by now.
 
starrigger's Avatar
 
Posts: 1,355
Karma: 1107383
Join Date: Aug 2008
Location: Massachusetts, USA
Device: Lenovo Yoga Tab Plus, Droid phone, Nook HD+
Quote:
Originally Posted by Jim Chapman View Post
I guess that - somehow- Freda's temp file got corrupted. Re-installing Freda doesn't clear the temp files (maybe it should ... but that isn't necessarily what you'd want to happen). Could you send me the /program files/freda/logfile.txt file, and I'll see if I can figure out what caused the problem.

The 'jittering' problem sounds like a memory space issue. Because of the crazy way that WinMo handles memory, you can get a situation where applications have trouble with memory because of which DLLs have been loaded by other applications (it's ugly!). And it can actually make a difference which order you run them in (i.e. launch app1 then app2 = no problem; launch app2 then app1 = app1 suffers memory allocation problems). And all the time the system would report that it has plenty of free memory (but behind the scenes some applications would not be able to use the supposedly 'available' memory). Could you have a think about whether that could possibly be happening in your case. Though to be honest, if it is, there may not be much I can do about it - Freda already tries to be as frugal as reasonably possible with memory allocation. But if you do find that the behaviour depends on which other applications are running, I'd be glad to receive details, and I can do a bit of analysis.

Windows Mobile 7 will sort this out by moving to a more rational memory model. I realise this may not be much of a comfort.

Thanks for using the program,

Jim
Okay, logfile attached. (At least, I think so.)

The whole process got delayed by my new laptop suddenly going all flaky on USB ports, which required some unscheduled IT work. I'm a little concerned that my Axim, with its patched-in version of WM6, may be causing problems.)

Anyway, I can't really tell you about what other apps might have been open or in what sequence. I generally have Mobipocket Reader open, as well, and I switch back and forth between what I'm reading there and what I'm reading in Freda. Aside from that, I periodically hit the buttons for Contacts, Calendar, etc., by accident and open up apps that I really don't want open. So really, it could have been anything.

Right now, I notice that the pages are changing pretty smoothly. Except that the finger-swipe method of changing page is not really usable, because most of the time my swipes open the menu rather than changing the page. Is there anything I can do to minimize that?

I think I'll look into that cleanRAM utility.

EDIT: I forgot to mention, the book that caused the trouble with Freda was one that I'd bought in mobipocket, but converted to epub in Calibre. I then unzipped it to fix an unclosed bold tag, and zipped it up again. I think I remember seeing others mention problems with Freda and books converted in Calibre.
Attached Files
File Type: txt logfile.txt (113.6 KB, 357 views)

Last edited by starrigger; 12-17-2009 at 10:40 PM.
starrigger is offline   Reply With Quote