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
cam_hal: throttle WARN spam so cam_task reduces it's stack footprint
Background
----------
• Every bad frame produced an ESP_LOGW():
- “Unexpected NULL frame …” (non-S3)
- “NO-EOI – JPEG end marker missing”
• Each ESP_LOGW() invokes vsnprintf() once ⇒ ~300 B of stack for that call.
What’s changed
--------------
* First occurrence of each warning:
ESP_DRAM_LOGW_ONCE() → zero stack after the first print.
* Subsequent occurrences:
count with a uint16_t and emit a **literal** ESP_LOGW() only
every 100th event (~ 60 B stack usage).
* Counters auto-reset at 10 000 to avoid wraparound.
* On ESP32-S3 the “Giving up GDMA reset…” message is also moved to
ESP_DRAM_LOGW_ONCE() to avoid stack usage.
Effects
-------
* Occasional diagnostics are still available: first warning and then a
summary every 100 events.
0 commit comments