[Zope-dev] Re: Memory Leak, and Changing Severity of a Bug

[Tres Seaver]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dan Pozmanter wrote:
> Yes, I saw the follow up.
> 
> So is there no way to change the severity of a bug?

It could be changed, but you need to persuade us that it is a
"showstopper" first.  Labeling the bug "critical" is a claim that we
have to fix it before making another release, which isn't reasonable
without a reproducible test case.

> Back to the bug.
> 
> ''' 
>    I was poking around in _Acquisition.c, and noticed my memory usage
> spiked.
> Returning to the vanilla code (2.8.2-final), I noticed the same spike
> (just less pronounced).
> (If you refresh the page a few gazillion times this pops up).
> ''' 
> In other words, this is happening in utterly unmodified c code.
> 
> Thanks for the link, I'll do some poking around.
> Is there a standard way for freeing the memory for the result of a
> Wrapper_findattr call from within _Acquistion.c?

See http://docs.python.org/api/countingRefs.html


Tres.
- --
===================================================================
Tres Seaver          +1 202-558-7113          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFDg5O++gerLs4ltQ4RArzfAKCzwxMi1sA3iHfT3ksQOPqYPv8wZgCfZ08T
2L9r5Ju8cnw51VZIEpgNYXQ=
=z2el
-----END PGP SIGNATURE-----