There are some processes known in unix as "runaways" that never stop and keep consuming resources forever.
Depending in what size of shared memory segment you have it's easy to get out of swap space (another good reason to stop reponding).
If it's CSPnsd YES, it's CSPgateway, if not, if it's cache process it can be something derived from errors in code that generate a big pipelining and freeze the machine.
Another interesting point is to check what's frozen: process (user), or machine (system) and see if you kill the process the machine recovers or not.
Nuno
Denver Braughler wrote:
Nuno Canas wrote:
You're saying it's CSPGateway, so is it CSPnsd daemon that is frozen !?
When there are crashes, odd and apparently unrelated behaviors can arise. I had trouble with Studio and Terminal pursuant to a crash during a CSP. Terminal would appear fine, but freeze up on a HALT.
