I have a problem with the STM32CubeIDE, it consumtion a lot of memory ram. In the task manager it open many conhost.exe process (i attach an imagen). Can you know how avoid open many conhost?. (sorry for my english)
I have a problem with the STM32CubeIDE, it consumtion a lot of memory ram. In the task manager it open many conhost.exe process (i attach an imagen). Can you know how avoid open many conhost?. (sorry for my english)
I've seen that when I compile the code all the conhost.exe processes are delete but after that, the conhost begin to open automatically like in the attach imagen.
CubeIDE is based on Eclipse, and Eclipse is known for it's generous memory consumption.
A text editor + commandline approach would be the least wasteful, but IDEs like IAR Workbench, Keil uVision, or Crossworks/Segger Embedded Studio are less profligate with host resources.
Yes, I know, but the System Workbench for STM32 is eclipse too and it doesn't have the problem of memory consumption (I attach an imagen), in the imagen the stm32cubeide is using more than 4.5 GB while System Workbench for STM32 just 948 MB. Maybe I have some wrong configuration in the stm32cubeide or some virus but windows defender has not detected anything. I tried uninstall and reinstall the stm32cubeide but the problem persists.
I'm working on Windows 7 /64 and I have the same problem. At starting the use of memoruy is 800 MB; If I create some test projects, the use of memory increase any time to some Gb over and over. Have you find the reason? (in that way ,I think, the processes go slow)
There is 16 GB memory in the workstation with this problem
The problem is not the amount of memory in workstation.
The problem is that STM32CubeIDE continuously makes new process threads of "Consulevensterhost", "WMI commandline Utility" and "Windows Command Processor". This increase the memory use of STM32CubeIde, with an empty workspace. So doing nothing, just starting the IDE with a new workspace.
Also my colleagues has this problem not with the same version of IDE.
It's look like a conflict with hardware or software on this workstation.