Memory Consumption Issue
-
I'm encountering a memory consumption issue with my Qt application, specifically a simple keyboard launcher. The application consists of an input line and a list view. Despite the simplicity of the application, I'm encountering a absurd memory consumption issue. (400mb)
I'd appreciate any guidance on how to optimize the memory usage of my Qt application. Are there any strategies or best practices I should follow to reduce memory consumption? Any help or suggestions would be greatly appreciated.

There are two frontend plugins based on Widgets and QML. Both suffer the same issue. With widgets the mem consumption is even worse.
-
And how do you measure the memory usage?
Keep in mind that if you're using a tool such as Windows task manager the memory usage is the working set size.
Applications (running processes) have larger working sets since that includes memory regions that are shared between processes (such as the memory pages used for loaded DLLs ) than what is their "memory" usage that the programmer sees as object allocation etc.
-
And how do you measure the memory usage?
Keep in mind that if you're using a tool such as Windows task manager the memory usage is the working set size.
Applications (running processes) have larger working sets since that includes memory regions that are shared between processes (such as the memory pages used for loaded DLLs ) than what is their "memory" usage that the programmer sees as object allocation etc.
@SamiV123 Yes i do use system monitors and htop. what else could I use? Working set or not, even if it is shared memory half a gig is way to much for such an application.
My goal is to understand where the memory consumption stems from. If it stems from shared resources I may decide to avoid whatever I can. Serioulsy a launcher should not take as much ram as a full blown IDE. -
@SamiV123 Yes i do use system monitors and htop. what else could I use? Working set or not, even if it is shared memory half a gig is way to much for such an application.
My goal is to understand where the memory consumption stems from. If it stems from shared resources I may decide to avoid whatever I can. Serioulsy a launcher should not take as much ram as a full blown IDE.@manuelschneid3r Use a proper memory analyzer like Valgrind