I have a task server running on AIR (for generating images and other
static website assets - it's part of a CMS) running on a local machine
that stays up for weeks. You'll have to find and fix any memory leaks,
or infinite event loops (and event handler build ups, etc.), and things
like that. AIR itself shouldn't have any problem running that long
(barring of course any uncovered bugs in uncovered corners of the AIR
API that you may uncover).
Of course, it can be pretty difficult to find this kind of stuff without
a good debugger and profiler - and debugging and profiling workflow.
The event stuff is probably the hardest part to manage in the Flash API
with regard to memory leaks. You really do just have to make sure to
unhook all the events once they are no longer needed - or even better,
just reuse the ones you set only once.
Kevin N.
On 11/23/12 5:27 AM, Paul A. wrote:
I've been asked about making a long-running app for a Samsung android
tablet.
In the past, I made one for a windows tablet but there was clearly a
memory leak (not that I could find it in my code) and after being
active for many, many hours it would hit a problem.
We looked at automating a restart of the app to get around this.
If I encounter the same issue on the Samsung, would I be able to
restart the app before it happens?
Or does anyone who has developed similar have any advice?
Thanks,
Paul
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
