Skip to content

Memory leak with ESP8266WebServer #152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
igrr opened this issue May 1, 2015 · 2 comments
Closed

Memory leak with ESP8266WebServer #152

igrr opened this issue May 1, 2015 · 2 comments

Comments

@igrr
Copy link
Member

igrr commented May 1, 2015

TODO: figure out where the does the pbuf get leaked

:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 91
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 103
:rn 103
:rn 103
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 103
:rn 31
:rn 103
:rn 103
:rn 268
:rn 268
:rn 204
:rn 103
:rn 103
:rn 103
:rn 111
:rn 31
:rn 204
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 111
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 268
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 268
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 31
:rn 91
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 268
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 245
:rn 31
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 91
:rn 31
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 81
Request: /heap
Args: 
:ref 2
:wr
:sent 51
:ww
:ur 2
:ur 1
:rn 31
:rn 95
:rn 46
:rn 245
:rn 72
:rn 72
beacon timeout
rm match
scandone
add 0
aid 2
cnt 
connected with LA LUNA LTE, channel 1
dhcp client start...
ip:192.168.1.30,mask:255.255.255.0,gw:192.168.1.1
:rn 95
:rn 95
beacon timeout
rm match
scandone
add 0
aid 2
cnt 
connected with LA LUNA LTE, channel 1
dhcp client start...
ip:192.168.1.30,mask:255.255.255.0,gw:192.168.1.1
:rn 77
:rn 100
:rn 165
:rn 100
:rn 100
:rn 100
:rn 100
:rn 100
:rn 95
:rn 95
:rn 65
:rn 101
:rn 101
:rn 101
:rn 65
:rn 266
:rn 266
:rn 65
:rn 266
:rn 266
:rn 65
:rn 266
:rn 243
:rn 77
:rn 243
:rn 72
:rn 42
:rn 95
:rn 95
:rn 95
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
:rn 393
Request: /inline
Args: 
:ref 2
:wr
:sent 63
:ww
:ur 2
:ur 1
WS:ac
:ref 1
WS:av
:ref 2
:ur 2
New client
WS:ac
:rcl
:rcla
Invalid request: 
:ur 1
:ref 1
WS:av
:ref 2
:ur 2
New client
:rcl
:rcla
WS:ac
:rn 393
WS:ac
Invalid request: 
:ur 1
:ref 1
WS:av
:ref 2
:ur 2
New client
Request: /inline
Args: 
:ref 2
:wr
:sent 63
:ww
:ur 2
:ur 1
:ref 1
WS:av
:ref 2
:ur 2
New client
:rcl
:rcla
Invalid request: 
:ur 1
:rn 102
:rn 102
:rn 95
:rn 95
@igrr igrr changed the title Memor Memory leak with ESP8266WebServer May 1, 2015
@holgerlembke
Copy link
Contributor

Here is how to see it the easy way: http://www.esp8266.com/viewtopic.php?f=28&t=3003

@igrr
Copy link
Member Author

igrr commented May 12, 2015

@holgerlembke that's a different issue — what you are referring to is #230 which is not actually a leak. TCP stack will free the memory once the connection exits the TIME_WAIT state.

@igrr igrr closed this as completed May 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants