[gs-bugs] [Bug 692372] Handle leakage when using GS9.00

[bugzilla-daemon at ghostscript.com]

http://bugs.ghostscript.com/show_bug.cgi?id=692372

Ken Sharp <ken.sharp at artifex.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
         AssignedTo|ken.sharp at artifex.com       |ray.johnston at artifex.com

--- Comment #4 from Ken Sharp <ken.sharp at artifex.com> 2011-07-25 10:59:08 UTC ---
With no arguments at all (just invoke gswin32), I see the handles increase by ~
2 per loop iteration. Which is broadly in line with what the customer reports.

The first of these is related to the ICC cache, it is allocated in
'gsicc_cache_new':

    result->wait = gx_semaphore_alloc(memory->stable_memory);

Each time we start up the interpreter we execute this code, which results in a
handle being used, which is never freed.

The other I haven't been able to track down yet, as it happens during
gs_interpret():

    code = gs_call_interp(pi_ctx_p, pref, user_errors, pexit_code,
                          perror_object);

This one is going to be much more difficult to track down, it also doesn't seem
to occur on every loop iteration, but that might be caused by the asynchronous
nature of running an external application to monitor the handles. It just may
not be updating fast enough.

I'm reassigning this to Ray for now, as I *think* the semaphore stuff was his.
If not maybe it should go to Michael, I'm uncertain. I have no idea who gets
the task of figuring out where the other handle leaks from.

-- 
Configure bugmail: http://bugs.ghostscript.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.