Is a killed process's state remembered?

[Avi Greenbury]

Sabniveesu Shashank wrote:
> Hi everyone!
>
> I killed a hanged "CodeBlocks IDE" process from Terminal. Now starting
> it again initiates a new process as shown in the output of 'top' --  but
> no window shows up. What actually is messed up?

It depends to some extent on what the CodeBlocks IDE was doing when it 
shut down - often this sort of thing is a result of it finding locks on 
resources that it doesn't expect, sometimes it's simply that a child 
process hasn't yet died and you need to either find it or wait for the 
system to finish cleaning up after stopping CodeBlocks' main process.

> A little more: Now that it has been 2 years for me since moving away
> from Windows, I understand that restarting is not always a solution as
> processes misbehaving, individually, could be killed. Pease answer me in
> this regard

I'm not sure what the question is; in general you're able to simply kill 
a misbehaving process. It's not always immediate, and nor is the tidying 
up of the child processes; Firefox has long been known for being killed 
and then taking many seconds before another instance can be successfully 
started. This is true of Windows, in the main, too, though.

-- 
Avi