search

bailuk / AAT

Another Activity Tracker for Android
https://bailu.ch/aat
GNU General Public License v3.0
150 stars 41 forks source link

Crash when device is on low memory (was: "Camera") #8

Closed spljaa closed 7 years ago

spljaa commented 7 years ago

Hi, I've problem that taking photo stops/terminates aat. Is this observed elsewhere? What kind of log/data could be helpfull to diagnose case? Regards Jan

bailuk commented 7 years ago

What device and Android version are you using? How do you know it terminates (and not just hides)? Does a message gets displayed? Does this happen with other apps too?

Also does this happen when taking a photo or when starting the camera app?

spljaa commented 7 years ago

Hi, Android 7.1, moto 2015g LineageOS nightly builds.

I retested it once again. And it is less deterministic than I was observing before. Today, AAT went gone (gone from status, and new track staryed when I launched app)when tracking was paused. But repeated test did not confirm it. I do not understand it, maybe there is some other factor I'm missing.

I've some experience with troubleshooting but nothing related to android. I'll plan test and count nubers. Maybe you have some tip how to create meaningful report. On other hand if you think it is just my device, then close the case.

Regards Jan

Dnia 21 maja 2017 16:07:14 CEST, bailuk notifications@github.com napisał(a):

What device and Android version are you using? How do you know it terminates (and not just hides)? Does a message gets displayed? Does this happen with other apps too?

Also does this happen when taking a photo or when starting the camera app?

-- You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub: https://github.com/bailuk/AAT/issues/8#issuecomment-302938934

-- Wysłane za pomocą K-9 Mail.

bailuk commented 7 years ago

You can use adb and logcat from the Android SDK to get a stack trace when AAT crashes. This would help me a lot.

Also note that AAT restores the last track after a crash.

spljaa commented 7 years ago

In my case track was not restored... Thus maybe it was something different. Today I tried it and it stopped just once. I would need some time to do tests properly. And I'm not sure how to filter logcat. Here are some greps that might be related to the problem. It shows some stack trace.

2160b.txt 4896.txt 32406.txt

bailuk commented 7 years ago

Thank you for your debugging effort.

There was a bug that gets triggered when the device is on low memory. It still is possible that AAT gets closed by Android when your phone is running out of memory. If this should happen you are welcome to open a new issue.

spljaa commented 7 years ago

Thanks for fixing it. I will test it. At least I hope way I build apk from sources was correct and will not introduce other problems