This generally occurs when another app is being run in the foreground which demands greater phone memory (RAM). When your app is put in the background while the user interacts with other applications, the OS can kill your app process if there’s not enough memory available for your application. This was until the application was brought back from the background tasks.Įvery android app runs in its own process and this process has been allocated some memory by the Operating System. The app seemed to work fine in normal testing conditions and the crash log was not replicable. While monitoring crash logs in production, I noticed some issues that were increasing day by day. This article talks about such issues and ways to solve them. Such crashes are unexpected and difficult to understand or process by just looking at the crash logs. In Android, you might have encountered a crash when you resume the app from the background state. Some crashes are encountered because of the system/platform it runs on irrespective of the business logic of the app.
It is an unpleasant experience to monitor these increasing crashes in your application when you have recently rolled out to production. Especially when these bugs result in apps crashing. If there’s anything common among all the developers out there, be it front-end, back-end, or even game developers, it is that we hate production bugs.
0 kommentar(er)
