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 low. This could lead to the object being deallocated too early, triggering segfaults when later accessed. Over repeated calls, these errors could accumulate, increasing the likelihood of a segfault.
Code paths in which the reference count of an object is left too high, leading to memory leaks
Code paths in which the reference count of an object is too low, but within an initialization routine, and thus likely to only happen once
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
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 a singleton object will be left too large. Technically incorrect, but unlikely to cause problems
These messages are often false-positives: the analysis tool has no knowledge about internal API calls that can lead to an exception being set