Yes this is most likely the process I was referring to. However there seems to be some misunderstanding on your part. I think this is the process that was running maybe a day or so ago. It ran for about 180 minutes or so at 100% cpu, and then it idled. Instead of idling this process should exit after it finishes processing. But what I'm guessing you did tonight is that you simply went back to this same exact process and continued working from it. The process is now running at 100% cpu which is fine. But when the commands that you've entered within that shell complete the process will be idling at 0% cpu, but it will still have all of the ram reserved. I don't know how else to explain this any clearer, but what you need to do is terminate all your dc_shell processes. In order to make sure they are all gone
you can type "ps aux | grep common_shell" (without the quotes) on the command line. if you get no results then all the processes are terminated. However if you do get some results you will have to kill the processes. To do this simply type "kill -9 <processID>". The value of <processID> is the 1st number you see after your user name when looking at the output of the "ps aux | grep common_shell" command. Once this is done all the processes are terminated. Next you need to edit the script that you are using to execute the commands within dc_shell. As the last command type "exit" and save the script. Open dc_shell and execute your script. This will cause the cpu usage to go to 100% and once the commands are done executing the dc_shell process will exit thereby freeing up all of the RAM that was allocated to it.