lwIP - A Lightweight TCP/IP stack - Bugs: bug #56806, Mem Leak in http_post_request
You are not allowed to post comments on this tracker with your current authentication level.
bug #56806: Mem Leak in http_post_request
Submitter: | schraubenkarl <schraubenkarl> | ||
Submitted: | Mon 26 Aug 2019 08:03:59 AM UTC | ||
Category: | apps | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Invalid |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 2.1.1 |
Mon 26 Aug 2019 08:23:37 AM UTC, comment #1: |
Stian Sebastian Skjelstad <mywave> |
Mon 26 Aug 2019 08:03:59 AM UTC, original submission:
After about 16 http POST requests pbuf_alloc returned NULL.
|
schraubenkarl <schraubenkarl> |
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-08-26 | gradator | Status | None | Invalid | |
Open/Closed | Open | Closed | |||
2019-08-26 | schraubenkarl | Carbon-Copy | - | Added schraubenkarl |
Powered by Savane 3.13-02a9.
Corresponding source code
http_post_rxpbuf sends the pbuf to http_post_get_response_uri
So, your callback is responsible for doing a pbuf_unref.
Your fix is a workaround for your callback not doing its job, in one of the code-paths. Take a look at the top two lines in your patch too: