Hi Brahmanathaswami,
What happens if you set the acceleratedRendering of the stack to false?
Best,
Panos
--
On Thu, Feb 16, 2017 at 9:08 PM, Sannyasin Brahmanathaswami via
use-livecode wrote:
> @ Jacque: I don't think it is ram after all.
>
> FYI: on my Nexus 5 I have 1.8 GB RAM and our new ap
@ Jacque: I don't think it is ram after all.
FYI: on my Nexus 5 I have 1.8 GB RAM and our new app + All of Googles "widgets"
that come preloaded take up a mere .8 GB and I have a full GB of RAM free.
after proceeding (as we discussed off list with our team) to delete stacks when
we move from on
On 2/14/17 3:38 PM, Richard Gaskin via use-livecode wrote:
J. Landman Gay wrote:
My other project is crashing on Android the same way. It also has heavy
server/internet use. I'm starting to think that's where the problem lies.
I wonder if that may be related to some of the leaks closed recent
J. Landman Gay wrote:
My other project is crashing on Android the same way. It also has heavy
server/internet use. I'm starting to think that's where the problem lies.
I wonder if that may be related to some of the leaks closed recently.
--
Richard Gaskin
Fourth World Systems
Software Desi
BTW, we're not talking about creating and deleting new stacks on the fly,
we mean the "delete stack" command that removes an open stack from RAM.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 14, 2
I frequently delete stacks when memory is an issue, which is the problem
with Swami's stack suite. I also create almost all new stacks with
destroystack set to true for the same reason.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://
Is there any reason to delete the stack? If not, don't. Clearly any CtoD should
be investigated, but I have never seen why an app would be designed to create
and delete stacks when all you have to do is show and hide existing ones.
Bob S
> On Feb 13, 2017, at 22:00 , Sannyasin Brahmanathaswam
On 2/14/17 12:00 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
Deleting stacks isn't helping. My Nexus 5 has 1 GB free RAM even with
all of Google's widgets and my app open and going from Stack B back
to stack A then deleting StackcB in 10 milliseconds is "nothing" in
terms of memory re
FWIW, tested on an android device with plenty of memory
Deleting stacks isn't helping. My Nexus 5 has 1 GB free RAM even with all of
Google's widgets and my app open and going from Stack B back to stack A then
deleting StackcB in 10 milliseconds is "nothing" in terms of memory
requirement, but
I'm trying to optimize for minimal RAM usage on mobile. The app is modular with
many stacks that are opened from the mainstack.
I had this before in a global library:
command portal_GoStack stackName
-- goes to the new stack
-- closes the current stack # But we want to delete it to clear RAM
--
10 matches
Mail list logo