Thanks for the video Simon, as always. One question: if we did all the memory-deallocating things correctly, then we should have only 0 or 1 Page objects, after entering a page multiple times, correct? So there is no way that even when doing everything correctly, more of the same page class exist in memory? To rephrase my question: is the 0or1 pages created a good indicator, that we did everything correctly with memory for a page?
What you found weird about the subscribtions object is that it is written "subscription". Nice video, btw. It's hard to find this kind of issues in the apps, and is not widely known, so these fixes are gold!
Great video. Simon, I hope you talk about Ionic with angularfire for performance. Why when using Angularfire with Ionic the app launch increases 3 seconds even use --prod tag New ionic app = 2 seconds on android New ionic app with angularfire = 5 seconds on android
the problem of memory leak is a bit deeper, in most cases it's about keeping the explicit refs to the unused structures. It might be achieved with promises as well. I'm sure that example with observable was used as "most common" in angular apps
I have an angular 8 SSR app that causes memory leaks on the server it keeps on increasing memory on the server when the application is in use and opened by many users. Even Unsubscribe all subscriptions on ngOnDestroy but doesn't work, still memory leaks persist Also there is no js intervals too Not able to find whats the issue and whats the correct way to solve the problem
Thank you, Simon. ^^ Your channel is my only resource for Angular and Ionic! :D
Happy to hear that Emre 🙏
Fantastic video. This knowledge is incredibly important as your grow your app. Thank you Simon!
My pleasure!
Thanks the Captain of Ionic. I really need this.
Thanks for the video Simon, as always. One question: if we did all the memory-deallocating things correctly, then we should have only 0 or 1 Page objects, after entering a page multiple times, correct? So there is no way that even when doing everything correctly, more of the same page class exist in memory?
To rephrase my question:
is the 0or1 pages created a good indicator, that we did everything correctly with memory for a page?
What you found weird about the subscribtions object is that it is written "subscription". Nice video, btw. It's hard to find this kind of issues in the apps, and is not widely known, so these fixes are gold!
Yeah I should have used plural - and glad you enjoyed the video!
Thank's Simon! It will help a lot here.
Glad it helped!
Great video. Simon, I hope you talk about Ionic with angularfire for performance.
Why when using Angularfire with Ionic the app launch increases 3 seconds even use --prod tag
New ionic app = 2 seconds on android
New ionic app with angularfire = 5 seconds on android
Perfect Video Find this at perfect time:) Thanks SIMON😊
So glad!
Good video Simon Thanks
If you use Promise instead of observable or convert the observable to a promise , does it resolve the problem of memory leak ?
the problem of memory leak is a bit deeper,
in most cases it's about keeping the explicit refs to the unused structures. It might be achieved with promises as well. I'm sure that example with observable was used as "most common" in angular apps
Good video thank's Simon 🙏.
Glad you enjoyed it!
I have an angular 8 SSR app that causes memory leaks on the server
it keeps on increasing memory on the server when the application is in use and opened by many users. Even Unsubscribe all subscriptions on ngOnDestroy but doesn't work, still memory leaks persist
Also there is no js intervals too
Not able to find whats the issue and whats the correct way to solve the problem
I have the same problem. Did you find the solution?
I would like to ask how to make an APP with short videos like Tiktok using ionic, because short videos are becoming more and more popular now
You can use a plugin to record videos, but not sure how you would implement the video editing functionality!
Hi Simon
👋
Google maps very slow 20k markers help me
Use less markers. Only show them for a specific radius, 20k is just too much to render I guess!
Ionic itself is a memory leak :p