Google needs to use these methods to fix the memory leaks in the RUclips Android app. Crashes every evening, after getting laggy and tetchy for a few minutes. Or perhaps they need to find leaks and fragmentation within Android itself. YT clearly degrades after a day or so of use. Works great after I kill and restart it. Classic leak behaviour, memory or some other resource, but it may be in support libraries an not the app itself. Lame.
Great Video, it helped me alot.. I followed your video and found out that there where unlimited numbers of variables instantiated inside a for loop and was not released which filled up the heap memory and even GC was not able to free up much space and the app results in crashing..So what should i do in this case..?
This helped find and fix memory leaks in my app that I was unaware of. Super, SUPER helpful. Thank you!
Why did you stop making video? This is really great content.
Hi! I am glad you like it! Lots of new videos are coming soon :-)
Hello, amazing content, please don't stop doing videos!
This really helped me a lot. Thank you so much! Just subscribed.
Keep making such simple videos.
Thanks brother watched it before now I needed it 😉
Thank you! We aslo have another option: Use Leak Canary to find memory leaks I think it's the easiest one)
wow this was amazing, please record more profiler videos.
Why are there applications that do not show the heap dump memory?
It's refreshed after using a movie or camera and going to another app, is there any solution?
VERY NICE, Talk about variables, how to best way to create them, THINKING about memory leak. THANKS
Such a nice course😍😍
hats off to you sir! Great explanation.
Great work Lukas :)
It was very useful video. Thanks for this.
simple yet helpfull! thanks
Absolutely brilliant video. thank you
Google needs to use these methods to fix the memory leaks in the RUclips Android app. Crashes every evening, after getting laggy and tetchy for a few minutes. Or perhaps they need to find leaks and fragmentation within Android itself. YT clearly degrades after a day or so of use. Works great after I kill and restart it. Classic leak behaviour, memory or some other resource, but it may be in support libraries an not the app itself. Lame.
Great Video, it helped me alot.. I followed your video and found out that there where unlimited numbers of variables instantiated inside a for loop and was not released which filled up the heap memory and even GC was not able to free up much space and the app results in crashing..So what should i do in this case..?
Hi! Glad you like it. I would need the full source code to be able to help you. Is it on GitHub?
@@lukaslechner Thanks for the concern... Problem has been solved...
How you sole the problem !@@joweltisso7365
Very usefull!!! thanks
thanks for shared it
Helpful
Informative Video..Great !!!
Super erklärt! Da lerne ich auch noch was :) lg
Danke, freut mich!
Clear
Nice