MobileRead Forums - View Single Post

geekmaster · 05-14-2016, 08:06 AM

The exec function is like a JUMP rather than a shell CALL, from scripts -- no new process space. However, the framework parent for KUAL is still eating lots of memory unless you shut it down when running native code. Though this is more important while running a build environment on the target device (why optware locked up on K5s, for example).

05-14-2016, 08:06 AM	#195
geekmaster Carpe diem, c'est la vie. Posts: 6,433 Karma: 10773670 Join Date: Nov 2011 Location: Multiverse 6627A Device: K1 to PW3	The exec function is like a JUMP rather than a shell CALL, from scripts -- no new process space. However, the framework parent for KUAL is still eating lots of memory unless you shut it down when running native code. Though this is more important while running a build environment on the target device (why optware locked up on K5s, for example). Last edited by geekmaster; 05-14-2016 at 08:13 AM.