lwip-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[lwip-devel] [bug #49392] TCP leaks memory when LWIP_TCPIP_CORE_LOCKING_


From: Yosic
Subject: [lwip-devel] [bug #49392] TCP leaks memory when LWIP_TCPIP_CORE_LOCKING_INPUT disabled.
Date: Sat, 17 Dec 2016 20:37:56 -0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:49.0) Gecko/20100101 Firefox/49.0

URL:
  <http://savannah.nongnu.org/bugs/?49392>

                 Summary: TCP leaks memory when LWIP_TCPIP_CORE_LOCKING_INPUT
disabled.
                 Project: lwIP - A Lightweight TCP/IP stack
            Submitted by: yosic
            Submitted on: Thu 20 Oct 2016 11:53:17 AM GMT
                Category: TCP
                Severity: 3 - Normal
              Item Group: Crash Error
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any
         Planned Release: None
            lwIP version: Other

    _______________________________________________________

Details:

I have embedded system that runs simple http server.
Every request(new connection) is served in separated thread and then socket
closes. I have about 30kb heap and it get exhausted after about 5000-7000
requests. Especially this reproduces when there are 3-5 or more simultaneous
requests to the server at once.
This issue is not reproduced when LWIP_TCPIP_CORE_LOCKING_INPUT is 1. So I
think there could be something connected with messages inside the stack since
LWIP_TCPIP_CORE_LOCKING_INPUT changes the execution flow to avoid using
messages.
I use v2.0.RC2




    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?49392>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]