You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a memory leak bug in some error handling code in ethernetif.c
/* full packet send to tcpip_thread to process */
if (netif->input(p, netif) != ERR_OK) {
LWIP_DEBUGF(NETIF_DEBUG, ("ethernetif_input: IP input error\n"));
p->l2_owner = NULL;
pbuf_free(p);
}
It is not correct to set p->l2_owner = NULL; before calling pbuf_free(p).
The same mistake is not present in wlanif.c.
The text was updated successfully, but these errors were encountered:
Alvin1Zhang
changed the title
Bug in lwip/port/esp32/netif/ethernetif.c
[TW#27236] Bug in lwip/port/esp32/netif/ethernetif.c
Nov 6, 2018
1. If L2_TO_L3_RX_BUF_MODE is not selected, we must assign l2_owner explictly before we call pbuf_free.
2. free intr resource in esp_eth_deinit
Closes#2670
catalinio
pushed a commit
to catalinio/pycom-esp-idf
that referenced
this issue
Jun 28, 2019
1. If L2_TO_L3_RX_BUF_MODE is not selected, we must assign l2_owner explictly before we call pbuf_free.
2. free intr resource in esp_eth_deinit
Closesespressif/esp-idf#2670
There is a memory leak bug in some error handling code in ethernetif.c
It is not correct to set
p->l2_owner = NULL;
before callingpbuf_free(p)
.The same mistake is not present in wlanif.c.
The text was updated successfully, but these errors were encountered: