Bug 988660 - libvirt handle leak
Summary: libvirt handle leak
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Virtualization Tools
Classification: Community
Component: libvirt
Version: unspecified
Hardware: x86_64
OS: Windows
unspecified
high
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-26 05:39 UTC by shichangyou
Modified: 2013-07-29 09:24 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-29 09:24:59 UTC
Embargoed:


Attachments (Terms of Use)

Description shichangyou 2013-07-26 05:39:09 UTC
Description of problem:

 the libvirt in windows will result in handle leak

Version-Release number of selected component (if applicable):

libvirt client version0.8.8 in win7
libvirtd using libvirt 0.8.5 in rhve 5.5

How reproducible:
 

Steps to Reproduce:
1. in win7 start the virsh.exe tool
2.  excute the list or dominfo command of virsh tool
3.  the handle of the process virsh.exe increase limitless

 i try to debug this bug, i find every call of prepareCall function in libvirt lib, it generate some mutex handle , but the libvirt do not destroy the unused mutex handle. 

 in prepareCall  it call virCondInit to new a mutex,  but it not call virCondDestroy, so the handle leak.   
  why??

Actual results:


Expected results:


Additional info:

Comment 1 Peter Krempa 2013-07-29 09:24:59 UTC
The libvirt version 0.8.8 is really old and since it was released we've done a couple releases that fixed quite a lot resource leaks. Please re-test if this issue still happens with the current upstream version. If it does happen please attach information about the leak from the debugging tool and also libvirt logs.

I'm closing this as fixed UPSTREAM. If it isn't fixed in the current upstream version, please re-open this bug.


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