Android Question App still in memory?

[ValDog]

Is there a way to detect, programatically, whether an app is still in memory? I find that if my app crashes it sometimes stays in memory - which complicates things when I run it again.

 

[Douglas Farias]

this is a bigproblem on b4a i m trying to understand this too =(
if i use firsttime to run layouts i cant close the current activity with activity.finish
and if i need reopen the closed activity i have layout not initializated

if i dont use firsttime the layout stay on the activity i can use activity.finish too
but when i open this 2 x have memory error *-*

 

[NJDude]

this is a bigproblem on b4a i m trying to understand this too =(

That has nothing to do with B4A, that's how Android works.

if i use firsttime to run layouts i cant close the current activity with activity.finish
and if i need reopen the closed activity i have layout not initializated

You are doing it wrong, you should NOT load layouts in FirstTime, that only triggers when the app runs for the VERY FIRST TIME.

 

[Douglas Farias]

You are doing it wrong, you should NOT load layouts in FirstTime, that only triggers when the app runs for the VERY FIRST TIME.

if i dont use i cant load my activity again because go load my layout again and again and this give me memory error *-*

 

[NJDude]

Then check your code, because that's how it's supposed to be done.

 

[Douglas Farias]

You are doing it wrong, you should NOT load layouts in FirstTime, that only triggers when the app runs for the VERY FIRST TIME.

1 exemple

make a main activity
make a login activity
make a register activity
and make a principal activity

OK TOTAL 4 LAYOUTS

now you open the app(main), click at register and open register activity.
ok later your register done go to principal and close the current activity (register).

now you is on the principal activity and you want make a logoff and register another account.

you close the principal activity and open register again. = Memory error because you is loading layout again
if you use first time here you have layout not initializated if you dont use have memory error

 

[NJDude]

Let me say it again: Then check your code.

 

[Douglas Farias]

Let me say it again: Then check your code.

yes i already see your post
http://www.b4x.com/android/forum/threads/app-still-in-memory.43087/#post-261424
lol

you have posted in the same time of me =)

 

[thedesolatesoul]

Is there a way to detect, programatically, whether an app is still in memory? I find that if my app crashes it sometimes stays in memory - which complicates things when I run it again.

Does your app crash or does your activity crash?

 

[thedesolatesoul]

if i dont use i cant load my activity again because go load my layout again and again and this give me memory error *-*

Always load layout in activity_create (not first time, not resume)
If the activity is loaded again, activity_Create will not run if it is already in memory. If it is not in memory it will run, but then the memory is empty anyway.

 

[Douglas Farias]

Always load layout in activity_create (not first time, not resume)
If the activity is loaded again, activity_Create will not run if it is already in memory. If it is not in memory it will run, but then the memory is empty anyway.

not realy look this sample i make here, run this 8 or 10x for u see

http://www.b4x.com/android/forum/th...ck-of-memory-with-video-and-sample-app.43097/

 

[Mrjoey]

dont debug in rapid mode , debug in legacy mode

 

[Erel]

Please don't make duplicate posts. See my answer there.