Why increase memory usage of running QApp, after executting Java JAR file in QProcess even if process done?
-
wrote on 13 Dec 2023, 08:10 last edited by
I have a problem with memory usage. This QApplication has commonly around 70 MB memory usage. In app I running many QProcesses (batch processing) in separate thread which executing java JAR file. Each process using from hundreds MB to 2-3 GB RAM. Each process increase app memory usage even if in system monitor its showed as separate process. After all processes finished, is memory usage of app not get back to 70 MB as before batch executed. I suppose that java garbage collector no clean. But why that occupied memory is assign to app from which was called java execution?
-
I have a problem with memory usage. This QApplication has commonly around 70 MB memory usage. In app I running many QProcesses (batch processing) in separate thread which executing java JAR file. Each process using from hundreds MB to 2-3 GB RAM. Each process increase app memory usage even if in system monitor its showed as separate process. After all processes finished, is memory usage of app not get back to 70 MB as before batch executed. I suppose that java garbage collector no clean. But why that occupied memory is assign to app from which was called java execution?
@JohnyB said in Why increase memory usage of running QApp, after executting Java JAR file in QProcess even if process done?:
I suppose that java garbage collector no clean
Has nothing to do with your app as you're running Java apps in other processes.
At what level does memory consumption stay after running these QProcesses?
It is normal that freed memory often stays assigned to the application.
You can also use memory profiling tools like Valgrind.
1/2