Leak checking "noise" caused by libnetapi.so
|Reported by:||ttcoder||Owned by:||nobody|
|Component:||Applications/Command Line Tools||Version:||R1/Development|
The simple fact of linking
-l netapi into an executable, results in 150 entries popping up in leak_check.sh even if just doing a launch-and-close of the program without actually using any network code , presumably due to some static variables in that library
These appear to be one-time "leaks", not recurrent ones, if so they wouldn't matter in term of memory usage.
What this ticket is about though, is this: they make it harder to hunt for leaks, as you have to wade through 150 additional entries (if I'm wrong about this, let's change component to kit/netkit)
To solve this, we don't necessarily have to "fix" the leaks per se, but instead could enrich the exception-list within leak_checker.sh to take those into account, much like it currently takes into account some other special cases in the support kit, ICU lib and so on