Replies: 6 comments 30 replies
-
I’d appreciate your help @jukkar @rlubos. I’m not sure if this is a Zephyr netstack issue or if I’m misusing it. |
Beta Was this translation helpful? Give feedback.
-
Did not spot anything obviously wrong in the application. Just wondering if setting |
Beta Was this translation helpful? Give feedback.
-
@ofirshe I used your source example (after some modifications) and I tried to use this with native_sim and that the server is not able to handle all the traffic (seems to work if I set the |
Beta Was this translation helpful? Give feedback.
-
@jacob-wienecke-nxp As you can see, this looks like a leak: the first three lines in net mem stay the same, even well after stopping the Python script. And the board doesn't respond any more. |
Beta Was this translation helpful? Give feedback.
-
@jukkar Should we open an issue now that @jacob-wienecke-nxp was also able to reproduce it on his side? I assume the reason it wasn’t reproduced on your side is due to latency - the |
Beta Was this translation helpful? Give feedback.
-
I was able to replicate the issue with |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I’m running a TCP server application (Zephyr v4.2-branch, NXP RT1061) that handles one client at a time: accept → read request → process → close → wait for next client. Under stress it becomes unresponsive and the TCP stack stops accepting new connections.
Server loop Structure
Stress script
Symptoms under load
After ~10 seconds of running the stress script:
The board cannot be pinged (both inbound and outbound).
The console repeatedly prints:
Shell diagnostics at that point
I'm seeing that when I reach this state, the stats in
net mem
andnet allocs
don’t change even if I stop sending traffic.My network configuration is as follows:
Would be grateful to get your help.
Beta Was this translation helpful? Give feedback.
All reactions