-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Sending a 50 byte long binary WebSocket frame crashes ESP32 #921
Comments
@collin80 I hate to tag you but it's mainly your CAN library forks (which you turned issues off on). Curious if you have any tips. |
The esp32_can repo certainly has "issues" enabled and I don't know of any reason you shouldn't be able to create an issue there. I checked and nothing seems out of place. If you believe it is crashing within that library or one of my other libraries then a decode of the crashdump might help. Otherwise, the issue you found in reference to deadlocks of the async_tcp task seems like a good avenue to pursue. |
@collin80 It's your |
[STALE_SET] This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions. |
[STALE_DEL] This stale issue has been automatically closed. Thank you for your contributions. |
I've tried everything from pinning functions to different cores via tasks, adding a scheduler, doing non-async, doing async.
Here is the code:
I load
http://192.168.4.1:8080/
in a web browser, pop the console, then dotransferData(50)
and I get this:Oddly enough,
transferData(40)
seems to work ok. I've already tried doingtesterPresent()
at different intervals (which is a 2 byte message). At 100ms, it is ok. At 50ms, the device crashes. Would love to hear some tips on how to tweak this. I quadruple checked the code for performance tweaks, not really seeing anything obvious.The text was updated successfully, but these errors were encountered: