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
Tracking the issue with timeouts / stack overflow due to buffer sizes issue in esp32 camera driver.
The issue manifests as no image received on Get still button call in case if high resolution and high quality is choose in the UI, with the scene capture in good lighting conditions with lots of details.
wait for a fix (if it will be fixed) in the esp camera
use config.frame_size = FRAMESIZE_UXGA; in StartCamera
call esp_camera_deinit + esp_camera_init on frame size change set_framesize
For most users of the esp32-cam-webserver # 2 workaround is the easiest to implement.
The text was updated successfully, but these errors were encountered:
MichaelXt
changed the title
StartCamera's default FRAMESIZE_SVGA causes stack overflow after set_framesize with bigger resolution is usedStartCamera's default FRAMESIZE_SVGA causes stack overflow during capture after set_framesize with bigger resolution is used
Mar 12, 2023
Sorry; I am not doing any further development on this project. it is old code and somewhat obsolete. I am currently working on retiring it; I will try to link to a more actively updated fork when I do.
Tracking the issue with timeouts / stack overflow due to buffer sizes issue in esp32 camera driver.
The issue manifests as no image received on
Get still
button call in case if high resolution and high quality is choose in the UI, with the scene capture in good lighting conditions with lots of details.The underlying issue is in esp camera driver:
espressif/esp32-camera#514
esp32-cam-webserver could either:
config.frame_size = FRAMESIZE_UXGA;
inStartCamera
set_framesize
For most users of the esp32-cam-webserver # 2 workaround is the easiest to implement.
The text was updated successfully, but these errors were encountered: