QUERY · ISSUE

constrained

openby peterhinchopened 2017-06-11updated 2017-07-02

docs

This has

gc.threshold((gc.mem_free() + gc.mem_alloc()) // 4)

which sets the threshold to 1/4 of the total RAM regardless of the amount allocated. Shouldn't this read

gc.threshold(gc.mem_free() // 4 + gc.mem_alloc())

to account for RAM already allocated?

CANDIDATE · ISSUE

gc_alloc_amount value not subtract by gc_free

closedby zxc199108opened 2020-07-15updated 2020-07-20

py-core

I find gc_alloc_amount just clear by gc_collect but，not subtract when gc_free. so the gc_alloc_amount is not accuracy. I suggest when MICROPY_GC_ALLOC_THRESHOLD == 1 ,we can compute gc_alloc_amount at gc_free.

Assessment

Q Qwen · medium

Both items concern MicroPython's garbage collection memory tracking, but they address different aspects. The query (issue 3138) is about a documentation example showing an incorrect formula for calculating the GC threshold - specifically whether the formula should account for already-allocated RAM. The candidate (issue 6245) is a bug report about the internal implementation of gc_alloc_amount not being decremented when gc_free() is called. While both relate to GC memory accounting, the query is about documentation correctness and threshold calculation logic, whereas the candidate is about a specific implementation bug in how allocation amounts are tracked. The candidate does not resolve the documentation issue raised in the query.

Suggested action

Keep both items open as they address different problems. The documentation issue (3138) should be addressed separately from the implementation bug (6245).

gc threshold calculation in docs/reference/constrained

gc_alloc_amount value not subtract by gc_free

Keyboard