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
It can happen that when large amount of data is sent through BLE indications (with lesser MTU, may be) this can cause problems of resource exhaustion at the BLE layer. As indications are acked, the next should be sent once the ack for the previous one is received.
This may be related: https://github.com/project-chip/connectedhomeip/issues/22416
cc @yufengwangca
Indications sent from a server also use a sequential indication-confirmation
protocol. No other indications shall be sent to the same client from this server
until a confirmation PDU has been received.
The text was updated successfully, but these errors were encountered:
Reproduction steps
It can happen that when large amount of data is sent through BLE indications (with lesser MTU, may be) this can cause problems of resource exhaustion at the BLE layer. As indications are acked, the next should be sent once the ack for the previous one is received. This may be related: https://github.com/project-chip/connectedhomeip/issues/22416 cc @yufengwangca
Bug prevalence
Not everytime. Can occur during stress tests
GitHub hash of the SDK that was being used
33f6a91
Platform
esp32
Platform Version(s)
No response
Type
Platform Issue
Anything else?
As per the BLE specification:
The text was updated successfully, but these errors were encountered: