I am somewhat confused regarding the call flow of `MqttClientNet_DeInit`.

[itmanlee]

I have a question: why is it that in version v2.0.0, the `MqttClientNet_DeInit` interface does not release `sockCtx->pfd[0]` and `sockCtx->pfd[1]`, as shown on the left side of the figure above?

[embhorn]

Hi @itmanlee

Thanks for contacting wolfSSL Support. The MqttClientNet_DeInit API is used to free resources allocated by MqttClientNet_Init

Releasing the socket resource is handled in MqttSocket_Disconnect, which is called from MqttClient_NetDisconnect

Could you tell us a bit about your project using wolfMQTT? We are always interested in hearing how the library is being used.

Thanks,
@embhorn - wolfSSL Support

[itmanlee]

Starting at line 2145 within the MqttClientNet_Init interface, a pipe (sockCtx->pfd) is created. I believe that the corresponding resource release should take place within the MqttClientNet_DeInit interface; these two interfaces should maintain a one-to-one correspondence—one for initialization and the other for de-initialization. Therefore, I still do not feel I have fully grasped the underlying logic.

[embhorn]

Hi @itmanlee

Thanks for clarifying. Okay, yes, I agree the pipe resource should be released in MqttClientNet_DeInit. I added a commit here to accomplish this:
e71c77c