out of memory on PCB

Toit

#out of memory on PCB

Thread channel in help

diego.ar 02/17/2025 07:17 PM

Hi, when running a Toit code on a PCB, i am getting an "allocation failed" error... see pls attached the error message

-----------------------------------
this is the function where i get the error, is a simple post thru http to a web server:

persist_data client data:
e := catch --trace:
response := client.post_json --host=URL --path=PATH {
"data": data
}

data_response := json.decode_stream response.body
print data_response
response = null
data_response = null
if e:
print "Error en POST: $e.stringify"

any tip to free memory resources?

thanks

floitsch 02/17/2025 07:20 PM

It does look like an actual OOM

floitsch 02/17/2025 07:20 PM

It's basically running out of memory when establishing the TLS connection.

floitsch 02/17/2025 07:21 PM

Is there anything else running?

floitsch 02/17/2025 07:22 PM

Independently, you could try to establish the connection earlier, when less memory is used. The really expensive part is establishing the connection. Once it exists you shouldn't need as much anymore.

floitsch 02/17/2025 07:24 PM

Also, if you don't use BLE use the esp32-no-ble envelope. Just having BLE support reduces the amount of free memory.

diego.ar 02/17/2025 08:11 PM

after flashing the device with no-ble, as per your suggestiion... jag flash esp32-no-ble --name device1 im getting a different out of memory error...

Heap report @ out of memory in primitive 6:2:
┌───────────┬──────────┬─────────────────────────────────────────────────────┐
│ Bytes │ Count │ Type │
├───────────┼──────────┼─────────────────────────────────────────────────────┤
│ 45056 │ 13 │ toit processes │
│ 16384 │ 4 │ system 0 601fdfa0-55bf-adc8-1620-cf4dba25ce57 │
│ 20480 │ 5 │ other 1 af3508f3-fd45-adf5-a3d6-b140bf7705bd │
│ 8192 │ 2 │ current 4 42e2be1a-805a-b594-6e2a-f7a6f4a75a7d │
│ 335872 │ 1 │ heap metadata │
│ 4096 │ 1 │ spare new-space │
│ 8608 │ 6 │ heap overhead │
│ 216 │ 3 │ event source │
└───────────┴──────────┴─────────────────────────────────────────────────────┘
Total: 393848 bytes in 16 allocations (9%), largest free 3692k, total free 3707k

Decoding by jag, device has version <2.0.0-alpha.174>

MALLOC_FAILED error.
0: Bus.test <sdk>\i2c.toit:84:5
1: Bus.scan <sdk>\i2c.toit:79:10
2: get-display get_display.toit:23:18
3: main lora_receive.toit:79:28
**
with the esp32-no-ble ... i get a malloc even before..

floitsch 02/17/2025 08:12 PM

Are you sure this is the same program? The get-display call was in comments in the code you showed me.(edited)

OPdiego.ar

after flashing the device with no-ble, as per your suggestiion... jag flash esp32-no-ble --name device1 im getting a different out of memory error... Heap report @ out of memory i...

floitsch 02/17/2025 08:13 PM

@bitphlipphar

what is the heap metadata?

diego.ar 02/17/2025 08:13 PM

it is yes the same program, i commented the display lines to make it run.. sorry ive sent the code commented to you

floitsch

@bitphlipphar what is the heap metadata?

bitphlipphar 02/17/2025 08:14 PM

Heap metadata is the extra bits we use to keep track of pointers in the heap. It is a percentage of the heap size.

bitphlipphar 02/17/2025 08:15 PM

Here the heap is pretty big, so we need a lot of space for the metadata.

floitsch 02/17/2025 08:15 PM

Unless I'm misreading the data, the heap metadata is reported as 335872 bytes which is much more than the actual heap