Timeline for Firmware gets stuck at obj.printto(client) in esp32
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2019 at 10:19 | comment | added | peeyush tekriwal | Understandable. I will add the code above | |
| Apr 29, 2019 at 9:25 | comment | added | Phil Haigh | @peeyushtekriwal I think you'll need to post your code for anybody to be able to help you further. | |
| Apr 26, 2019 at 17:45 | comment | added | peeyush tekriwal | I did the testing and the heap doesn't seem to be the issue. After a successful transfer, there is still about 75% of the heap memory available. | |
| Apr 26, 2019 at 15:38 | comment | added | peeyush tekriwal | I will surely log the heap size but this doesn't seem to be happening as the code is not getting corrupted or even crashing. Just that after some time it throws a handle_error and resumes to what it should be doing. However, I will still log the heap size and watch the deviations. | |
| Apr 26, 2019 at 13:40 | review | First posts | |||
| Apr 26, 2019 at 14:32 | |||||
| Apr 26, 2019 at 13:39 | history | answered | Phil Haigh | CC BY-SA 4.0 |