You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi developing team!
My name is Carlos Silva, I’m a student of Computers and Systems Engineering at “Universidad de los Andes” in Bogota, Colombia. During this first semester of the year me and my teammates (Juan Jose Beltran and Camilo Falla) have been analyzing your app for a course. We have been using it, getting familiarized with it and reading all the code that you have in this repository. The purpose of this was to see if we could find enhancements to your code and app features and suggest changes on it. Previously, my teammate Juan Jose created an issue regarding eventual connectivity in your app, now, I wanted to suggest another change that could make your job as developers easier in detecting memory leaks on your app. While profiling your app, we saw that you have a great management of the memory on the device, there is not excessive use of the GC and the memory doesn’t overloads easily. Although, as we know, there are many possible memory leaks that are hard to detect to the naked eye. That is why we wanted to recommend you use a library that we think it might be useful to enhance your app, this library is called Leak Canary. Here the only thing that you have to include is in your build.gradle the following code.
dependencies {
// It has to be on debugImplementation
debugImplementation 'com.squareup.leakcanary:leakcanary-android:2.11'
}
// CS, JB, CF
This will allow you to use the library automatically. This will allow you to find leaks in destroyed activity instances, fragement instances, view instances, viewmodel and service instances.
We hope you can implement this library, and hope to hear from you, and if you found it useful.
Best regards,
Carlos Silva, Camilo Falla, Juan Jose Beltran.
The text was updated successfully, but these errors were encountered:
Hi developing team!
My name is Carlos Silva, I’m a student of Computers and Systems Engineering at “Universidad de los Andes” in Bogota, Colombia. During this first semester of the year me and my teammates (Juan Jose Beltran and Camilo Falla) have been analyzing your app for a course. We have been using it, getting familiarized with it and reading all the code that you have in this repository. The purpose of this was to see if we could find enhancements to your code and app features and suggest changes on it. Previously, my teammate Juan Jose created an issue regarding eventual connectivity in your app, now, I wanted to suggest another change that could make your job as developers easier in detecting memory leaks on your app. While profiling your app, we saw that you have a great management of the memory on the device, there is not excessive use of the GC and the memory doesn’t overloads easily. Although, as we know, there are many possible memory leaks that are hard to detect to the naked eye. That is why we wanted to recommend you use a library that we think it might be useful to enhance your app, this library is called Leak Canary. Here the only thing that you have to include is in your build.gradle the following code.
This will allow you to use the library automatically. This will allow you to find leaks in destroyed activity instances, fragement instances, view instances, viewmodel and service instances.
We hope you can implement this library, and hope to hear from you, and if you found it useful.
Best regards,
Carlos Silva, Camilo Falla, Juan Jose Beltran.
The text was updated successfully, but these errors were encountered: