Hi,

I have a question. Suppose I write a short terminal program, say in C/C++, and compile it with gcc/g++. Then I go to the output file in dolphin and double click it. Dolphin displays a prompt asking if I'd like to execute it and I click "Execute". What would be the Standard input, output and error for this program?


The reason I ask is because I was playing around with a program like this and I must have done something (I'm trying to figure out what) that made the program run in the background writing output to .xsession-errors until that file was 305 GB (I only noticed when I got a notification that my disk was full). I'm curious how that happened.

Thank you,
Isaac

Ok, I figured something out! If you run a program from dolphin as I described, it appears to run in the background, but no activity occurs. If you open KSysGuard and look at the process it shows that it's not using any CPU. It's just listed there as a child process of Dolphin. But if you now close that dolphin instance, its child process will keep running. Unlike before, for some reason there will now be a steady input of zeroes in the input stream of the process. This means the process will be receiving input and might use lot of CPU. Also, if the process has any output, it seems to get redirected somehow to .xsession-errors.

Perhaps everyone knows this already. But I wonder, what can be done to prevent having orphan child processes of dolphin hanging around in the system after an instance of that program closes?

sounds like a bug to me, could you please report this on https://bugs.kde.org