View Single Post
Old 11-18-2012, 04:13 PM   #289
eureka
but forgot what it's like
eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.eureka ought to be getting tired of karma fortunes by now.
 
Posts: 713
Karma: 2290994
Join Date: Dec 2011
Location: north (by northwest)
Device: Kindle Touch
I guess, force closing of WAF app is the memory management.

WAF app is essentially a html page rendered by WebKit engine with a thin layer of Kindle-specific API exposed through special JavaScript object. When you execute your own JavaScript in context of your WAF app, you can create memory leaks. Though JavaScript implementation provides garbage collector (i.e. automatic memory management), it's possible to create memory leaks in JavaScript program. With many memory leaks (or with one repeated memory leak), memory consumption grows, and at some point your WAF app will be terminated, because on terminating all memory consumed by [any] application will be freed.

You should check free memory size with free command at the start of your app and at the end of stress test to confirm you hypothesis.

Last edited by eureka; 11-18-2012 at 04:15 PM.
eureka is offline   Reply With Quote