ESP-IDF with Insights problem with diagnostics

[filzek]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

We are getting some field returns in esp-insights dashboard that is direct related to this error:

0x401231bf
0x401231bf: esp_diag_heap_metrics_init at D:/project/managed_components/espressif__esp_diagnostics/src/esp_diagnostics_heap_metrics.c:183

the dashboard says:

15/02/25 10:11:59
heap: string at ROData: 0x3f41a9a8 PC: 0x401231bf

heap
heap: string at ROData: 0x3f41a9a8 PC: 0x401231bf
0x401231bf
We could not find the firmware image to cross-reference this log entry. Please upload a firmware image to get cross-referenced information for this log entry.

but when we ran
xtensa-esp32-elf-addr2line -pfiaC -e project.elf 0x401231bf

it shows that the problem is with the
0x401231bf
0x401231bf: esp_diag_heap_metrics_init at D:/project/managed_components/espressif__esp_diagnostics/src/esp_diagnostics_heap_metrics.c:183

Should not the insights tell exact what happen to bring the exception and cause the crash?

Actual behavior (suspected bug)

seens that or esp-insights is not correct registering the bug or the bug is within the esp-insights/diagnostics framework by itself.

Error logs or terminal output

Steps to reproduce the behavior

Latest ESP-IDF 5.4
commit 5c75a994dad84b49065b41efa1df6a6e90a9055f (HEAD -> release/v5.4, origin/release/v5.4)
Merge: 8deb26be27 8e8d922edc
Author: Marius Vikhammer marius.vikhammer@espressif.com
Date: Mon Feb 10 14:45:15 2025 +0800

Merge branch 'fix/esp-event-profiling_v5.4' into 'release/v5.4'

fix(esp_event): Fix event loop profiling in handler_execute function (backport v5.4)

See merge request espressif/esp-idf!36684

Esp insights 1.2.3 diagnostics 1.2.1

Project release version

1.2.3

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Windows

Operating system version

windows 11

Shell

CMD

Additional context

No response

[filzek]

maybe the diagnostics should not follow the insights rule as of:

#if (CONFIG_SPIRAM_SUPPORT && (CONFIG_SPIRAM_USE_CAPS_ALLOC || CONFIG_SPIRAM_USE_MALLOC))
#define MEM_ALLOC_EXTRAM(size) heap_caps_malloc_prefer(size, 2, MALLOC_CAP_DEFAULT | MALLOC_CAP_SPIRAM, MALLOC_CAP_DEFAULT | MALLOC_CAP_INTERNAL)
#define MEM_CALLOC_EXTRAM(num, size) heap_caps_calloc_prefer(num, size, 2, MALLOC_CAP_DEFAULT | MALLOC_CAP_SPIRAM, MALLOC_CAP_DEFAULT | MALLOC_CAP_INTERNAL)
#define MEM_REALLOC_EXTRAM(ptr, size) heap_caps_realloc_prefer(ptr, size, 2, MALLOC_CAP_DEFAULT | MALLOC_CAP_SPIRAM, MALLOC_CAP_DEFAULT | MALLOC_CAP_INTERNAL)
#else
#define MEM_ALLOC_EXTRAM(size) malloc(size)
#define MEM_CALLOC_EXTRAM(num, size) calloc(num, size)
#define MEM_REALLOC_EXTRAM(ptr, size) realloc(ptr, size)
#endif

to allocate memory in place of just direct?

not sure if the crash is related to direct memory related or if it is related to process a corruption, so no guess at all