esp32_camera: Set framebuffer task prio to 1 #5943
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this implement/fix?
Prio 0 is the lowest possible, competing with the idle task. All non-idle tasks should have a prio > 0. If there's another task at prio > 0 around (like the application's loop task), it is possible the framebuffee task never gets executed.
Perhaps the prio should even be above 1, to keep avoid missing frames.
This came to attention during review of eliminating the delay in the application's main loop in case the loop is already slow (#5869).
Code is untested due to lack of hardware.
Types of changes
Related issue or feature (if applicable): fixes
Pull request in esphome-docs with documentation (if applicable): esphome/esphome-docs#
Test Environment
Checklist:
tests/
folder).If user exposed functionality or configuration variables are added/changed: