[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

I don't know whether I have reported this before:

When the garbage collector discovers a garbage JOB array it seems to
perform a .uclose on it causing an inferior job to go away.  This is
incorrect and annoying.  It is incorrect because it is not the case
that the job has become inaccessable just because it's superior has
forgotten about it for the moment, you can connect to the SAME job
with another JOB array later. It is annoying because it can cause jobs
to vanish without anyone explicitly asking for it.