Closed wuqingzheng closed 3 years ago
When building a connection, if the MQTTDecoder receives an incorrect message or code, it will be thrown to the business through the delegate. If reconnected at this point, the MQTTDecoder is reinitialized, and it is possible to release the MQTTDecoder, resulting in an access-wild pointer Crash.
The latest version has been modified here to address this issue, 3Q
Thank you very much for your developed [MQTT Client - Framework] (https://github.com/novastone-media/MQTT-Client-Framework), we are trying to use it, but shows the firebase crash a lot.
The version we used before was 0.9.2, and there were many crashes after going online, so we checked the issue and found the issue [#325](-[MQTTDecoder stream:handleEvent:] crashing with EXC_BAD_ACCESS KERN_INVALID_ADDRESS #325)
Therefore, we chose to update the version. Due to the change of interface, we chose to update to version 0.10.0, but there were still very, very many Crashes.
Then, we found that the [Add fix for crash when decoder deallocated] (https://github.com/robnadin/MQTT-Client-Framework/commit/de8982dad71da98fa6de98b00535bb81c8f3f4a8), so finally have been solved this problem? If we update to 0.15.3, will we not Crash?