You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
is the limit on SCHEDULED_FN_MAX_COUNT 32 still reasonable in the light of increased use for scheduled interrupts? Of the top of my mind, using scheduled interrupts for SW Serial, there are a lot of interrupts in a short interval of time :-)
The text was updated successfully, but these errors were encountered:
@dok-net the reason for this limit is that alloced nodes don't ever get freed. Instead, they get saved for recycling.
The original code had a limit of 10 (if memory serves). When this code was updated, we decided on a limit of 32. The thinking was that, if you have to queue more than 32 callbacks before unwinding in the loop, you probably have bigger problems in your sketch that should be solved first.
So, before the limit is increased, I'd like to see a real(istic) example of how the current limit of 32 can be hit. Can you please provide one?
CoopTask can use cores/esp8266/Schedule for round-robin scheduling, but the device won't handle as many tasks to let the 32 limit become a problem. @devyte There's still no copyright notice.
Arduino/cores/esp8266/Schedule.h
Line 9 in 95fd7b5
@hreintke What is your opinion on:
The text was updated successfully, but these errors were encountered: