Let's say I initialize a bunch of stuff inside onCreate and then bring the app into the background for an hour. What happens if Android frees stuff that was initialized inside onCreate when I continue using the app? Will onCreate be called again? I'm asking because I consider to move some stuff inside onResume instead of onCreate, which is non necessary in case onCreate is called again.
Android - What happens when android frees up memory of data that was created in onCreate
61 Views Asked by TheGreatCornholio At
1
There are 1 best solutions below
Related Questions in ANDROID
- Creating global Class holder
- Flutter + Dart: Editing name of a tab shows up a black screen
- android-pdf-viewer Received status code 401 from server: Unauthorized
- Sdk 34 WRITE_EXTERNAL_STORAGE not working
- ussd reader in Recket Native module
- Incorrect display of LinearGradientBrush in IOS
- The Binary Version Of its metadata is 1.8.0, expected Version is 1.6.0 build error
- I can't make TextInput to auto expand properly in Android
- Creating multiple instances of a class with different initializing values in Flutter
- How to create a lottie animation
- making android analyze with coverity sast tool
- Flutter plugin development android src not opening after opening example
- I initialize my ViewModel in the Activity with several fragments as tabs, but the fragments(tabs) return null for the updated livedata
- Node.js Server + Socket.IO + Android Mobile Applicatoin XHR Polling Error...?
- How I can use the shared preferences class?
Related Questions in ANDROID-LIFECYCLE
- Can't find Transformations in androidx.lifecycle
- Activity unable to observe second livedata object within viewmodel
- Android BottomsheetDialogfragment lifecycle goes to onStop in android version <=12 & onPause >= 13 when ImagePicker is opened
- java.lang.IllegalStateException: No instantiated fragment for (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx) crash in Android
- java.lang.illegalargumentexception: cannot add the same observer with different lifecycles
- unable to collect Stateflow in Lifecycle aware manner in onCreate function of a fragment
- How to Prevent Timeout Timer from Starting During System Prompts in Android App
- LifecycleStartEffect.onStopOrDispose is called twice on navigating to another screen
- CanvasFrontBufferRenderer is giving error as APP_SCOUT_WARNING
- Process is not killed even after swiping off from the recents screen
- kotlin-coroutine can not be launched
- Activity instance does not refill again after onDestroy
- update include tag data when app theme changed (recreating Activity)
- Clicking overview(recent) button on android device doesn't call onPause() and onStop() method. Why is that?
- Compose View Not Recomposing on state changes
Related Questions in ANDROID-MEMORY
- How to create a memory dump of an android emulator?
- How to know when memory is free'd after onTrimMemory callback in Android?
- Is there a way to find out the cause of occasional huge memory usage spike?
- How to prevent leaking Fragment
- Crash: "Check failed: mem_map_.IsValid() couldn't allocate <US_MALE_NAME> stack."
- Android native memory leak related to MediaCodec
- will Passing Android activity to a dependency ( a variable in the same class ) cause Memory Leaks
- Why ComponentCallbacks2.TRIM_MEMORY_RUNNING_CRITICAL when the available memory is high?
- Restart App when in memory variable values are cleared
- How do you efficiently manage texture memory in OpenGLES on Android?
- Callback from registerForActivityResult not called when fragment is destroyed
- Memory Leak in Custom Alert dialog animation Android
- Android UnknownHostException even there is an active and working internet connection
- What is the definition of type A and type B Android services?
- How to solve frequent garbage collection in android?
Trending Questions
- UIImageView Frame Doesn't Reflect Constraints
- Is it possible to use adb commands to click on a view by finding its ID?
- How to create a new web character symbol recognizable by html/javascript?
- Why isn't my CSS3 animation smooth in Google Chrome (but very smooth on other browsers)?
- Heap Gives Page Fault
- Connect ffmpeg to Visual Studio 2008
- Both Object- and ValueAnimator jumps when Duration is set above API LvL 24
- How to avoid default initialization of objects in std::vector?
- second argument of the command line arguments in a format other than char** argv or char* argv[]
- How to improve efficiency of algorithm which generates next lexicographic permutation?
- Navigating to the another actvity app getting crash in android
- How to read the particular message format in android and store in sqlite database?
- Resetting inventory status after order is cancelled
- Efficiently compute powers of X in SSE/AVX
- Insert into an external database using ajax and php : POST 500 (Internal Server Error)
Popular # Hahtags
Popular Questions
- How do I undo the most recent local commits in Git?
- How can I remove a specific item from an array in JavaScript?
- How do I delete a Git branch locally and remotely?
- Find all files containing a specific text (string) on Linux?
- How do I revert a Git repository to a previous commit?
- How do I create an HTML button that acts like a link?
- How do I check out a remote Git branch?
- How do I force "git pull" to overwrite local files?
- How do I list all files of a directory?
- How to check whether a string contains a substring in JavaScript?
- How do I redirect to another webpage?
- How can I iterate over rows in a Pandas DataFrame?
- How do I convert a String to an int in Java?
- Does Python have a string 'contains' substring method?
- How do I check if a string contains a specific word?
In general, Android does not do that. Android may terminate your process, in which case everything is gone and you will start over from scratch on the next app launch.
However, if your process manages to survive for the hour in the background, most everything will be right where you left it. Some libraries might specifically try to release some memory when your app moves to the background (e.g., caches in an image-loading library), to try to reduce the likelihood that your process will be terminated to free up system RAM.
The documentation has a bit of material on the process lifecycle.
If Android terminated your process, then yes,
onCreate()of any started activity will be called again. If your process survived, the activity is already created, so it will not getonCreate()called again.onStart()andonResume()would be called in either case.The documentation has some material on the activity lifecycle.