When creating a task, after several calls to websocket_write (inside a task, not a callback) the communication is aborted, and the program appears to fail creating the new task according to the selected uri. A change in the quantity of attempts was observed.
With 256 stack each task, the problem presented itself after 15 calls. With 1024 stack each task, the problem appeared after only 4 calls (the pattern is clear). This was independent of the not-websocket-calling task, which continued to work flawlessly, regarding of the problem on the other tasks.
When creating a task, after several calls to
websocket_write(inside a task, not a callback) the communication is aborted, and the program appears to fail creating the new task according to the selected uri. A change in the quantity of attempts was observed.With 256 stack each task, the problem presented itself after 15 calls. With 1024 stack each task, the problem appeared after only 4 calls (the pattern is clear). This was independent of the not-websocket-calling task, which continued to work flawlessly, regarding of the problem on the other tasks.