7/29/24 - Tests W/ Memory Info

Baseline Test:

This is what memory usage looks like with normal qgroundcontrol-herelink without a payload. Here I click on a bunch of tabs and zoom on the map. Notice the memory usage goes up as expected when more resources are needed (map tiles being loaded, tabs being loaded, etc)

• This is what the memory usage of the app looks like without any payload. During this, I did a few reboots of the vehicle and I also was swapping applications. Both things did not influence memory usage. What did was scrolling out on the map (expected since each map tile is loaded into the scene), and clicking on tabs. Clicking on a tab looks to be allocating memory and then keeping it allocated once clicking off, but clicking multiple times will not allocate additional memory. So it seems that QT will keep tabs unloaded until first time clicked.

  

Text might be hard to read. The first area of text is where I start scrolling around the map, which leads to expected memory spike. The second text references when I open "Application Settings" for the first time. The third piece of text is when I am tabbed out. This data shows that under normal usage without a payload, the application appears to be stable in terms of memory usage. Increase of memory usage happens when more resources are loaded which is completely expected.