Mailinglist Archive: zypp-devel (149 mails)

< Previous Next >
Re: [zypp-devel] Re: libzypp-bindings (python) memory leak of type 'zypp::ResPool *'
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Thu, 4 Sep 2008 10:33:15 +0200
  • Message-id: <20080904083315.GA20081@xxxxxxxxxxxxx>
* Michael Andres <ma@xxxxxxx> [Sep 04. 2008 10:31]:
On Wed, Sep 03, Klaus Kaempf wrote:

* Jan-Simon M?ler <dl9pf@xxxxxx> [Sep 03. 2008 20:44]:
Hi Klaus, hi list !

mypool = zy.pool()
swig/python detected a memory leak of type 'zypp::ResPool *', no
destructor found.

Yeah, libzypp does not provide a destructor since there's no reason
for it. If the ResPool is gone, libzypp is gone ;-)

That's not true ;)

ResPool is just an interface to 'The Pool' singleton. ResPool objects can
be created and deleted as needed. They contain no data except for the
pointer to the implementation. That's why they don't need a destructor.

Then I wonder why SWIG does not create (resp. find) a destructor for

To unsubscribe, e-mail: zypp-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: zypp-devel+help@xxxxxxxxxxxx

< Previous Next >