[zypp-devel] libzypp-bindings (python) memory leak of type 'zypp::ResPool *'

newer
[zypp-devel] libzypp client...

older
[zypp-devel] [Patch] building...

Jan-Simon Möller

3 Sep 2008 3 Sep '08

18:44

Hi Klaus, hi list !

...

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

I got it working but next stop is to query the pool, which fails. best regards Jan-Simon -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Show replies by date

Klaus Kaempf

3 Sep 3 Sep

19:56

New subject: [zypp-devel] Re: libzypp-bindings (python) memory leak of type 'zypp::ResPool *'

* Jan-Simon Möller [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 ;-) Swig can probably be fooled by defining an empty ResPool destructor.

...

I got it working but next stop is to query the pool, which fails.

The query interface (to satsolver) has undergone quite some changes. I just got an initial swig binding for satsolver working. Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Michael Andres

4 Sep 4 Sep

08:31

New subject: [zypp-devel] Re: libzypp-bindings (python) memory leak of type 'zypp::ResPool *'

On Wed, Sep 03, Klaus Kaempf wrote:

...

* Jan-Simon M?ler [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. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma@novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

Klaus Kaempf

08:33

New subject: [zypp-devel] Re: libzypp-bindings (python) memory leak of type 'zypp::ResPool *'

* Michael Andres [Sep 04. 2008 10:31]:

...

On Wed, Sep 03, Klaus Kaempf wrote:

...
* Jan-Simon M?ler [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 ResPool. Klaus -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org

5714

Age (days ago)

5715

Last active (days ago)

List overview

Download

3 comments

3 participants

participants (3)

Jan-Simon Möller
Klaus Kaempf
Michael Andres