Version: 4.5 (using KDE 4.5.4) OS: MS Windows On MS Windows when a KDE app is started, there are many background-apps like dbus-daemon.exe, kglobalaccel.exe, klauncher.exe and kioslave4.exe. On Windows 7 each of them starts an instance of conhost.exe (a control process on Windows 7 for the command prompt) which can add up to more than 20 conhost.exe processes running for one single KDE application. Reproducible: Always Steps to Reproduce: start a KDE app on Windows 7 and have a look in a task manager. http://www.howtogeek.com/howto/4996/what-is-conhost.exe-and-why-is-it-running/
Does this restrict you in any way? Those processes you mentioned probably are console processes (I haven't checked), I don't see why we should change that atm since this has more implications than just switching a flag.
I don't have a problem with these conhost processes (my Computer has a lot of RAM), but since konqueror starts a lot of kioslave processes there are a lot of conhost processes, each of them using 2.6 MB of RAM. I had the case of 64 (!!) conhost processes, which adds to 166 MB of RAM. As there are no console windows this is useless, since the conhost process only adds drag and drop support to a console window.
How are you measuring the RAM usage? I mention this because even on Windows multiple instances of the same application share memory that is identical so I find it very unlikely that each individual conhost process uses a unique 2.6 MB of RAM. The effect you describe is still undesirable, but it might not be as bad as you think.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!