This is a summary of errors seen when compiling with an experimental static analysis tool
Raw build logs can be seen here
The triager didn't know how to classify these ones
_imaging.c | _getbbox | passing uninitialized data (D.17819) as argument 3 to function at _imaging.c:1780 |
Code paths in which the reference count of an object is left too high, but within an initialization routine, and thus likely to only happen once
_imaging.c | init_imaging | ob_refcnt of PyStringObject is 1 too high |
Code paths in error-handling that will lead to a segmentatation fault (e.g. under low memory conditions)
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
_imaging.c | _getcolors | ob_refcnt of new ref from (unknown) getpixel 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