lwIP - A Lightweight TCP/IP stack - Bugs: bug #55477, possible memory leak with sockets
You are not allowed to post comments on this tracker with your current authentication level.
bug #55477: possible memory leak with sockets
Submitter: | Michael Zimmers <mzimmers> | ||
Submitted: | Mon 14 Jan 2019 11:26:11 PM UTC | ||
Category: | sockets/netconn | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Invalid |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | Other |
Tue 15 Jan 2019 05:50:49 PM UTC, comment #1: |
Michael Zimmers <mzimmers> |
Mon 14 Jan 2019 11:26:11 PM UTC, original submission:
Hi all -
|
Michael Zimmers <mzimmers> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 2 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-01-15 | goldsimon | Status | None | Invalid | |
Open/Closed | Open | Closed |
Powered by Savane 3.13-4448.
Corresponding source code
Found the problem -- as a networking newbie, I didn't realize that I needed to call freeaddrinfo() after using getaddrinfo(), and the example I borrowed from didn't have that.
Can someone please either delete my bug report, or mark it as cockpit error? I'd do it myself, but I don't know how...