Sniffer: heap check on a real controller

Open
#37 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
cpp

Research direction

Read item 10 in .specs/sniffer.md and compare results with the reviewed heap data linked in issue #30. On the maintainer’s controller, record free heap, largest block, and minimum free heap before and after a scan that finds new IDs, with the page open and a second web client connected, then through an OTA update. If minimum free heap drops below about 20 KB, shrink the history pool first.

Written by the indexing model from the issue text.

Description

Spec: Acceptance criteria, item 10. Needs the maintainer and the controller.

On the maintainer's controller, in a single boot: record heap free, largest block and min free before and after a scan that finds new IDs, with the page open plus a second web client, and through an OTA update. Compare with the reviewed heap data.

If min free drops under ~20 KB, shrink the history pool first.

Dominant language
C++
Stars
8
Forks
4
Avg merge
15h 58m
Merged PRs (30d)
5

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from distante/esphome-components

All issues in distante/esphome-components

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.