lwIP - A Lightweight TCP/IP stack - Bugs: bug #62160, MEM_OVERFLOW_CHECK,...
You are not allowed to post comments on this tracker with your current authentication level.
bug #62160: MEM_OVERFLOW_CHECK, MEM_STATS_DISPLAY and mem_trim
Submitter: | Jonathan D <jona> | ||
Submitted: | Wed 09 Mar 2022 02:03:38 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | None |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Open | Planned Release: | None |
lwIP version: | 2.1.2 |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
Carbon-Copy List
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.
No changes have been made to this item
When MEM_OVERFLOW_CHECK is activated, the "used" memory provided by MEM_STATS_DISPLAY increased every time the "mem_trim" is called (by 32 bytes at a time, MEM_SANITY_REGION_BEFORE and _AFTER are both 16 bytes).
The "used" memory remains constant when MEM_OVERFLOW_CHECK is deactivated.
I though at first that there was a memory leak in my code but now, I'm more into thinking that the issue is in MEM_STATS although I didn't spot exactly what is wrong.