CesiumGS
Memory Leaks
When creating new Cesium Viewer in an Angular app, JS heap doesn't get cleared on page change. when navigating between the pages the bug seems to appears(refreshing the page clears the heap memory). Below is the sample app attached cesium_angular.zip.
Application Installation steps:
npm install
ng serve
App running on http://localhost:4200
Steps to reproduce:
- Click on the button CLICK ME on the new_page.
- Click on the button CLICK ME on the globe page. Reproduce these steps 3-4 times and then check the chrome dev performance page.
Screenshot Chrome Performance Tab
The main issue which I am facing is that when I am trying to load high resolution images, it loads 2-3 times but after that webpage crashes. (memory never clears on page change, It keeps on increasing until the page crashes)
Have you guys noticed how much memory your JulianDate component uses? It's extreme, a large percent of a large project. I used Firefox DevTools to grab a snapshot of memory 1) upon initial load of our app using Cesium, then 2) upon subsequent page unloads/reloads. Each reload of the page accumulates much more memory (MBs). Record CallStacks, and aggregate the data by CallStack, then drill down into rows using the largest number of bytes. Almost without fail: JulianDate.
I am seeing this as well on my angular application. Any progress or updates on this issue? Or is there anyway I can assist with solving this issue as a potential contributor?
Hi @patrickgoldstein, there hasn't been any activity on this recently. We haven't done a proper profile within the context of an angular app ourselves.
If you are interesting in contributing, it would be helpful to profile and identify the problem areas.
