Bug 3082 - context leak
: context leak
Status: NEW
: XIO
Globus XIO
: development
: Other Linux
: P3 normal
: ---
Assigned To:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-04-05 16:25 by
Modified: 2005-09-28 08:54 (History)


Attachments
valgrind-report.txt (3.78 KB, text/plain)
2005-04-05 16:26, Joe Bester
Details


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-04-05 16:25:07
I've been tracking down leaks in C hosting and found one which appears to be 
an XIO one. I'll attach a valgrind report.
------- Comment #1 From 2005-04-05 16:26:01 -------
Created an attachment (id=561) [details]
valgrind-report.txt

The 2nd leak is the one of interest here (globus_i_xio_context_create)
------- Comment #2 From 2005-04-07 11:13:09 -------
Here are some more (hopefully useful details):   
   
The context leak seems to stem from a bug handling driver_operations. In this   
particular case, it is a write operation synthesized from a handle_cntl. In   
the callback for the write, globus_xio_driver_operation_destroy() is called,  
but the reference count for the context is not decremented because the  
operation's reference count is not 0 (the outstanding reference is the write  
callback which hasn't returned yet). 
 
joe 
------- Comment #3 From 2005-09-28 08:53:12 -------
Joe, can you write what client(s) did you run in addition to the container?
I tried running all tests, but it didn't show up the leakage you meant.