[ branch: eps32 ] during own and onboard to the cloud, lot's of memory is consumed

[WAvdBeek]

[ branch: eps32 ] during own and onboard to the cloud, lot's of memory is consumed
Open

[ branch: eps32 ] during own and onboard to the cloud, lot's of memory is consumed

As I mentioned during own and onboard heap memory was very consumed. To produce logs I applied patch print_debug.patch

And heap size:xyz occurs every second and describe how many memory is available at the esp32.

Own and Onboard proceeded without crash or abort for memory.

Logs: esp32_just_works_1.log esp32_mfg_1.log

Drop or upload designs to attach

Linked issues
0

heunggu, ahn
heunggu, ahn @ansee7221 · 5 months ago
@jkralik, The log file does not contain IPV6 content in response to the client. I would like to ask if IPV6 response is not available.

DEBUG: C:/Users/admin/source/repos/iotivity-lite/messaging/coap/engine.c <coap_receive:166>: coap://10.112.112.36:59745 ~ Outgoing message of size 1059 bytes to coap://0.0.0.0:0-->coap://10.112.112.36:59745

Edited by heunggu, ahn 5 months ago
Jozef Kralik
Jozef Kralik @jkralik · 5 months ago
Developer
Here is logs from onboarding tool with actions:

Discover via realm IPv6
Own the device
Provision identity certificate
RETRIEVE /oic/sec/cred
RETRIEVE /oic/sec/acl2
Provision auth-crypt RW access to NCRs
RESET device
The previous logs comes from go-sdk which proceed more actions than OBT.

esp32_just_works_onboarding_tool_ipv6.log

Kishen Maloor
Kishen Maloor @KISHEN · 5 months ago
Maintainer
@jkralik

Granted that go-sdk Client may be doing more, but an attempt at an apples to apples comparison of the heap size at the end of onboarding suggests a ~130K free heap with go-sdk and ~160K free heap with the onboarding_tool. It may help to understand why that might be the case.

heunggu, ahn
heunggu, ahn @ansee7221 · 5 months ago
I'm trying to do "Discover" in the IPv6 scope, but there is not response from IUT.

=> This was a configuration issue.

Edited by heunggu, ahn 5 months ago
farid
farid @farid · 3 months ago
I see the same issue... one one the root cause are the number of tls sessions and in esp32 one tls session is 32K by default. This can be reduced but it depends on the server ability to handle tls fragment negociation (Amazon does not)

David Marquez
David Marquez @DavidMarquezUPC · 2 months ago
In my case I can't even onboard successfully, the app crashes with the following. I guess it has to do with esp32 running out of memory

A2 : 0x00000750 A3 : 0x00000750 A4 : 0xffffffff A5 : 0x00000000
A6 : 0x00000000 A7 : 0x00000000 A8 : 0x00000068 A9 : 0x00000750
A10 : 0x00000000 A11 : 0x3ffbc890 A12 : 0x3ffdabb9 A13 : 0x000000bf
A14 : 0x3ffdc7b8 A15 : 0x3ffdabb8 SAR : 0x0000000a EXCCAUSE: 0x0000001c
EXCVADDR: 0x0000075c LBEG : 0x4000c46c LEND : 0x4000c477 LCOUNT : 0x00000000

Backtrace:0x400ea88c:0x3ffb8c80 0x400f008a:0x3ffb8cc0 0x400e9ecd:0x3ffb9ce0 0x400ec641:0x00000000 |<-CORRUPTED
0x400ea88f: oc_process_baseline_interface at /home/david/iot-lite/iotivity-lite/api/oc_server_api.c:147

0x400ea88c: oc_process_baseline_interface at /home/david/iot-lite/iotivity-lite/api/oc_server_api.c:146

0x400f008a: get_csr at /home/david/iot-lite/iotivity-lite/security/oc_csr.c:42

0x400e9ecd: oc_ri_invoke_coap_entity_handler at /home/david/iot-lite/iotivity-lite/api/oc_ri.c:953

0x400ec641: coap_receive at /home/david/iot-lite/iotivity-lite/messaging/coap/engine.c:529
David Marquez
David Marquez @DavidMarquezUPC · 1 month ago
Nevermind I was using a newer version of esp-idf, which was probably causing the issue. I followed the installation steps in the README again (they were updated a few weeks ago) and now cloud works. It does use up a lot of memory though