Opened 3 years ago

#12701 new enhancement

Leak checking "noise" caused by libnetapi.so

Reported by: ttcoder Owned by: nobody
Priority: normal Milestone: R1
Component: Applications/Command Line Tools Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

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

Attachments (1)

fallout_from_libnetapi_linkage.txt (70.2 KB) - added by ttcoder 3 years ago.
(ignore the last 2 entries, they're caused by my app not the lib -- we're talking of 150 entries total not 152)

Download all attachments as: .zip

Change History (1)

Changed 3 years ago by ttcoder

(ignore the last 2 entries, they're caused by my app not the lib -- we're talking of 150 entries total not 152)

Note: See TracTickets for help on using tickets.