Skip to content
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

wifi: esp_at: sockets not cleaned up on close #43512

Closed
JordanYates opened this issue Mar 8, 2022 · 1 comment · Fixed by #44889
Closed

wifi: esp_at: sockets not cleaned up on close #43512

JordanYates opened this issue Mar 8, 2022 · 1 comment · Fixed by #44889
Assignees
Labels
area: Networking area: Wi-Fi Wi-Fi bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Comments

@JordanYates
Copy link
Collaborator

Describe the bug

The ESP_SOCK_IN_USE flag is never cleared when a socket is closed.
Therefore after ESP_MAX_SOCKETS (5) sockets are opened and closed, esp_socket_get will fail to allocate another socket.

Expected behavior
Closing a socket should result in a complete cleanup of all resources, allowing it to be opened again at a later time.

Environment (please complete the following information):

  • Zephyr v2.7.1
  • Zephyr v3.0.0
@github-actions
Copy link

github-actions bot commented May 8, 2022

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: Networking area: Wi-Fi Wi-Fi bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants