04-17-2016, 05:37 PM
(This post was last modified: 04-17-2016, 06:11 PM by Alan Evans.)
(04-17-2016, 03:04 PM)Zuberman Wrote: I believe I may have located the issue. Certain conditions can trigger requests from the Android OS for my app to release some memory (like if it's in the background or the device is almost out of RAM). In response to those requests, I free up resources, but some of those may be actively in use. I believe this creates a situation in which pages can not render or be rendered incorrectly. I'm certainly seeing this while trying to print large PDFs. I'm going to be changing the code to either safely free up resources, or just not free them at all to ensure that the program can never enter a bad state.
Mike
This sounds encouraging, Mike. Without sounding like a blithering idiot (as I have no idea how much work is involved making the changes you'd need to make), is there any chance an update would be available within the next 9 hours? That would give me just enough time to update MSP on the tragically slow WIFI network available within the theater and hopefully do the show without any further drama. Thanks so much for all your efforts!
Please let me know.
PS Just checked and saw that this Acer puter takes a max. of 4 gig RAM. So stuck there.