Hi,
I just ran into a situation where after a prolonged time of use with live VATSIM traffic+ATC data displayed, Charts PC “application” started to consume significant CPU power (~40% on a 3800X according to task manager) and around 4.5GB RAM. Looks like a memory leak and a quite busy loop somewhere.
Let me know wether I can take any diagnostics when/if that happens again.
Best regards,
Daniel
I observed the same, especially a significant high CPU utilization when using VATSIM “Traffic” Option. “ATC” does not cause this high utilization.
Memory consumption does increase approx. 100 MB per 2 minutes.
Maybe, but it seems to need a trigger. My charts client is running now for an hour or so with live VATSIM traffic and still only around 20MB RAM used.
Hi,
Thank you for the input. We’re looking at ways to optimize performance here. It doesn’t seem to be a memory leak but rather linked to the amount of traffic. We’ll see what we can do to improve this.
Regards,
Stephen
Hello!
We have indeed identified a potential memory leak! The situation should be much improved in the latest v8.38.0 release. Give it a go, and let us know what you think!
Kind Regards,
Malte
Seems better, but not fully solved. I’ve seen the process grow to around 800MB again, although not to 4GB as before.
Growing to a certain extent is fully expected, but it should not be uncontrolled. It should stabilize! Have you seen the app crash to a white screen with this update? That was a result of the previous memory leak.
Not yet. And about expected growth: I have it running now for a good hour with traffic display enabled and I’m seeing the process using about 20MB RAM, stable. Why should it suddenly grow to 800MB?!?
I am happy to hear that you have yet to encounter any issue related to a memory leak!
To be perfectly honest, 20MB of RAM sounds much less than I would expect from our app! We are using Electron, which is not exactly known for its small memory footprint. On top of that, we are running a map engine that is closer to a game engine than a map viewer, as well as optionally tracking thousands of aircraft in real-time - with several different icons having to be loaded into memory for display.
I would expect anything from 400MB at idle to around 800MB under use, but it should no longer be leaking memory! If you see anything that looks like a leak - particularly if the app becomes slower and slower over time and finally crashing, please let us know!
Kind Regards,
Malte
Absolutely, I was wondering about 20MB as well. Coming from the age of CBM8032 with it’s whooping 32kbytes of RAM I know how to develop software to be memory efficient, but I wasn’t expecting modern software to be that lean with all the library and framework bloat of today. 
And indeed you’re right, I was relying on the Task Manager “Processes” tab which shows this:
But when switching to “Details”, I see significantly different data, which is probably much closer to the truth:
Haha yeah, times have changed since then and not always for the better! But computers have a lot more memory today and it certainly has become easier to achieve what was previously much harder technology-wise, so at least there’s that!
Now that looks more like what I’d expect too! Let us know if there are any leaks! We’re looking good in that regard so far based on what we can see from our POV.
