This is a summary of errors seen when compiling with an experimental static analysis tool
Raw build logs can be seen here
Code paths in which the reference count of an object is left too high, leading to memory leaks
| sesearch.c | print_av_results | ob_refcnt of '*list' is 1 too high |
Code paths in which the reference count of an object might too large - but in which the reference in question came from a function not known to the analyzer.
The analyzer assumes such references are new references, but if the function returns a borrowed reference instead, it's probably not a bug
| sesearch_wrapper.c | wrap_sesearch | ob_refcnt of new ref from (unknown) sesearch is 1 too high |
These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set
| sesearch.c | print_av_results | returning (PyObject*)NULL without setting an exception |