ESP32 Forum

Posted: **Sat Feb 03, 2018 6:31 pm**

Hi,

This became rather lengthy, please bear with me.

Assuming Heap Debugging is set to "Comprehensive", when allocating a block of memory (multi_heap_malloc()), an additional poison_head_t and poison_tail_t are allocated. Then, it goes on to poison the allocated buffer in poison_allocated_region(), setting the head and tail with HEAD_CANARY_PATTERN (0xABBA1234) and TAIL_CANARY_PATTERN (0xBAAD5678), respectively. When back in multi_heap_malloc, we call verify_fill_pattern(), to verify that the buffer in between head an tail contains the FREE_FILL_WORD (0xfefefefe), and replacing it with MALLOC_FILL_WORD (0xcececece)

First question: What fills the memory with 0xfe in the first place?

Ok, so we now know that whenever we allocate a buffer, we can expect it to be filled with 0xce, correct?

Moving on to freeing memory.

Again, assuming that Heap Debugging is set to "Comprehensive", when freeing a block of memory (multi_heap_free()), the region being freed is verified via verify_allocated_region() such that the head and tail values are intact, i.e. no buffer under/overruns have happened (at least none that wrote any data). Next, the entire buffer, including head and tail are filled with 0xfe, after which the entire buffer is handed back to the heap.

All correct so far?

Now, to my actual problem. I am consistently (as in 100%) getting the stack trace at the bottom of this post very shortly after start up.

First off, I've replaced cJSON with version 1.7.1 as 1.6.0 which ships with ESP-IDF has a memory bug which causes a too small buffer to be allocated.

While calling cJSON_free in smooth::core::json::Value::to_string[abi:cxx11]() in Value.cpp:285 (using default mapping to free()) I expect that to eventually call function multi_heap_free(), which it seems to do just before entering newlib-code (the line numbers seems off once it enters this part of the code):

Code: Select all

0x4012bc71: __assert_func at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdlib/../../../.././newlib/libc/stdlib/assert.c:59 (discriminator 8)

0x40088dbf: multi_heap_free at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

Deeper in the stack it also wants to allocate a block of memory for whatever reason(?), which eventually ends up in the corrupt heap message and total stop.

A newly allocated block should have a tail value of 0xBAAD5678, which the message also states, but look closer at what it got:

Code: Select all

CORRUPT HEAP: Bad tail at 0x3ffe04d1. Expected 0xbaad5678 got 0xcececece

That is the MALLOC_FILL_WORD, the value used to fill the buffer between head and tail in multi_heap_malloc()/verify_fill_pattern().

I 'm not certain that I'm right, but I've literally spent days with cppcheck, valgrind and -fsanitize trying to come to the conclusion that the error lies in my code and not in the code for heap poisoning, but I always come back to the later one over and over. The read failing value in the tail is no random number, it is always MALLOC_FILL_WORD and there is no user code that ever writes that specific value.

I've also attempted to use a breakpoint to stop the application when it hits 0x3ffe04d1:

Code: Select all

esp_set_watchpoint(0, (void *)0x3ffe04d1, 4, ESP_WATCHPOINT_STORE);

If I set it at the very start of the program, it seems the memory is first accessed by the Wifi:

Code: Select all

0x4013d814: tcpip_adapter_set_hostname_api at /home/permal/esp/esp-idf/components/tcpip_adapter/./tcpip_adapter_lwip.c:1150

V (1566) Task: Task 'I2CTask' initialized
Guru Meditation Error: Core  0 panic'ed (Unhandled debug exception)
Debug exception reason: Watchpoint 0 triggered 
Core 0 register dump:
PC      : 0x40088c92  PS      : 0x00060a36  A0      : 0x80088d74  A1      : 0x3ffcea30  
0x40088c92: verify_fill_pattern at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

A2      : 0x3ffe04d0  A3      : 0x000005d8  A4      : 0xcececece  A5      : 0x00000001  
A6      : 0x00000001  A7      : 0xfefefefe  A8      : 0x3ffe0aa8  A9      : 0x00000001  
A10     : 0x00000001  A11     : 0x3ffe3ff9  A12     : 0x00003548  A13     : 0xfefefefe  
A14     : 0x00003b9c  A15     : 0x00000000  SAR     : 0x00000018  EXCCAUSE: 0x00000001  
EXCVADDR: 0x00000000  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000000  

Backtrace: 0x40088c92:0x3ffcea30 0x40088d71:0x3ffcea60 0x40082e74:0x3ffcea80 0x40082ea5:0x3ffceaa0 0x40083349:0x3ffceac0 0x4000beaf:0x3ffceae0 0x4008535d:0x3ffceb00 0x400f1481:0x3ffceb20 0x400f085d:0x3ffceb50 0x400ec422:0x3ffcebb0
0x40088c92: verify_fill_pattern at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

0x40088d71: multi_heap_malloc at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

0x40082e74: heap_caps_malloc at /home/permal/esp/esp-idf/components/heap/./heap_caps.c:136

0x40082ea5: heap_caps_malloc_default at /home/permal/esp/esp-idf/components/heap/./heap_caps.c:136

0x40083349: _malloc_r at /home/permal/esp/esp-idf/components/newlib/./syscalls.c:37

0x4008535d: wifi_malloc at /home/permal/esp/esp-idf/components/esp32/./wifi_internal.c:28

0x400f1481: esf_buf_alloc at ??:?

0x400f085d: wdevProcessRxSucDataAll at ??:?

0x400ec422: ppTask at ??:?

Setting the same breakpoint slightly prior to where cJSON_free is called (as in the problem description above), like so:

Code: Select all

std::string Value::to_string()
            {
                esp_set_watchpoint(0, (void *)0x3ffe04d1, 4, ESP_WATCHPOINT_STORE);
                auto* p = cJSON_Print(data);
                esp_clear_watchpoint(0);
                std::string s{p};
                cJSON_free(p);
                return s;
            }

it seems that cJSON_print() is the culprit:

Code: Select all

Guru Meditation Error: Core  0 panic'ed (Unhandled debug exception)
Debug exception reason: Watchpoint 0 triggered 
Core 0 register dump:
PC      : 0x40088c92  PS      : 0x00060636  A0      : 0x80088d74  A1      : 0x3ffbe800  
0x40088c92: verify_fill_pattern at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

A2      : 0x3ffe04d0  A3      : 0x00000094  A4      : 0xcececece  A5      : 0x00000001  
A6      : 0x00000001  A7      : 0xfefefefe  A8      : 0x3ffe0564  A9      : 0x00000001  
A10     : 0x00000001  A11     : 0x3ffe3ff9  A12     : 0x00003a8c  A13     : 0xfefefefe  
A14     : 0x00003b9c  A15     : 0xff000000  SAR     : 0x0000001e  EXCCAUSE: 0x00000001  
EXCVADDR: 0x00000000  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000000  

Backtrace: 0x40088c92:0x3ffbe800 0x40088d71:0x3ffbe830 0x40082e74:0x3ffbe850 0x40082ea5:0x3ffbe870 0x40083349:0x3ffbe890 0x4000beaf:0x3ffbe8b0 0x40193370:0x3ffbe8d0 0x40193b1c:0x3ffbe920 0x40174777:0x3ffbe940 0x401206c7:0x3ffbe960 0x40120878:0x3ffbeab0 0x40110809:0x3ffbead0 0x4015e80a:0x3ffbeb10 0x4015ea17:0x3ffbec40 0x4011265c:0x3ffbeca0 0x400d1112:0x3ffbfc30
0x40088c92: verify_fill_pattern at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

0x40088d71: multi_heap_malloc at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

0x40082e74: heap_caps_malloc at /home/permal/esp/esp-idf/components/heap/./heap_caps.c:136

0x40082ea5: heap_caps_malloc_default at /home/permal/esp/esp-idf/components/heap/./heap_caps.c:136

0x40083349: _malloc_r at /home/permal/esp/esp-idf/components/newlib/./syscalls.c:37

0x40193370: print at /home/permal/esp/esp-idf/components/json/library/cJSON.c:82

0x40193b1c: cJSON_Print at /home/permal/esp/esp-idf/components/json/library/cJSON.c:82

0x40174777: smooth::core::json::Value::to_string[abi:cxx11]() at /home/permal/code/G2-Alarmsystem/components/Smooth/core/json/Value.cpp:282

0x401206c7: G2Alarm::event(AnalogValue const&) at /home/permal/code/G2-Alarmsystem/components/Smooth/include/smooth/core/ipc/TaskEventQueue.h:90

0x40120878: non-virtual thunk to G2Alarm::event(AnalogValue const&) at ??:?

0x40110809: smooth::core::ipc::TaskEventQueue<AnalogValue>::forward_to_event_queue() at /home/permal/code/G2-Alarmsystem/components/Smooth/include/smooth/core/ipc/TaskEventQueue.h:90

0x4015e80a: smooth::core::Task::exec() at /home/permal/code/G2-Alarmsystem/components/Smooth/core/Task.cpp:131

0x4015ea17: smooth::core::Task::start() at /home/permal/code/G2-Alarmsystem/components/Smooth/core/Task.cpp:56

0x4011265c: app_main at /home/permal/code/G2-Alarmsystem/main/./main.cpp:21

0x400d1112: main_task at /home/permal/esp/esp-idf/components/esp32/./cpu_start.c:455


CPU halted.

And yes, if I don't call cJSON_Print(), I no longer have an issue. However, I can also just not start a task that literally only sleeps in the current use case and the issue also "goes away". I'm not sure what this tells us.

If I'm looking at all this the wrong way, please tell me. No one will be happier than me if it is possible to limit the search for this issue to my own code.

Update:
I'm currently running the exact same code with "Light impact" mode in which the part where it writes the *_FILL_WORD bytes to the buffer is disabled and I'm not getting any issues with destroyed tails.

This is the complete stacktrace from which the snippets above are taken:

Code: Select all

CORRUPT HEAP: Bad tail at 0x3ffe04d1. Expected 0xbaad5678 got 0xcececece
CORRUPT HEAP: multi_heap.c:370 detected at 0x3ffe04d8
abort() was called at PC 0x400889bb on core 0
0x400889bb: multi_heap_assert at /home/permal/esp/esp-idf/components/heap/./multi_heap.c:339
 (inlined by) multi_heap_malloc_impl at /home/permal/esp/esp-idf/components/heap/./multi_heap.c:370


Backtrace: 0x40089108:0x3ffbe3e0 0x400892ab:0x3ffbe400 0x400889bb:0x3ffbe420 0x40088d5d:0x3ffbe440 0x40082e74:0x3ffbe460 0x40082ea5:0x3ffbe480 0x40083349:0x3ffbe4a0 0x4000bbc2:0x3ffbe4c0 0x4005918d:0x3ffbe4e0 0x40058d62:0x3ffbe540 0x40130002:0x3ffbe560 0x4012bd01:0x3ffbe820 0x4012bc71:0x3ffbe870 0x40088dbf:0x3ffbe8a0 0x40082f62:0x3ffbe8c0 0x40083355:0x3ffbe8e0 0x4000bec7:0x3ffbe900 0x40193cae:0x3ffbe920 0x40174785:0x3ffbe940 0x401206c7:0x3ffbe960 0x40120878:0x3ffbeab0 0x40110809:0x3ffbead0 0x4015e7fe:0x3ffbeb10 0x4015ea0b:0x3ffbec40 0x4011265c:0x3ffbeca0 0x400d1112:0x3ffbfc30
0x40089108: invoke_abort at /home/permal/esp/esp-idf/components/esp32/./panic.c:648

0x400892ab: abort at /home/permal/esp/esp-idf/components/esp32/./panic.c:648

0x400889bb: multi_heap_assert at /home/permal/esp/esp-idf/components/heap/./multi_heap.c:339
 (inlined by) multi_heap_malloc_impl at /home/permal/esp/esp-idf/components/heap/./multi_heap.c:370

0x40088d5d: multi_heap_malloc at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

0x40082e74: heap_caps_malloc at /home/permal/esp/esp-idf/components/heap/./heap_caps.c:136

0x40082ea5: heap_caps_malloc_default at /home/permal/esp/esp-idf/components/heap/./heap_caps.c:136

0x40083349: _malloc_r at /home/permal/esp/esp-idf/components/newlib/./syscalls.c:37

0x40130002: _vfiprintf_r at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdio/../../../.././newlib/libc/stdio/vfprintf.c:865 (discriminator 3)

0x4012bd01: fiprintf at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdio/../../../.././newlib/libc/stdio/fiprintf.c:50

0x4012bc71: __assert_func at /Users/ivan/e/newlib_xtensa-2.2.0-bin/newlib_xtensa-2.2.0/xtensa-esp32-elf/newlib/libc/stdlib/../../../.././newlib/libc/stdlib/assert.c:59 (discriminator 8)

0x40088dbf: multi_heap_free at /home/permal/esp/esp-idf/components/heap/./multi_heap_poisoning.c:339

0x40082f62: heap_caps_free at /home/permal/esp/esp-idf/components/heap/./heap_caps.c:136

0x40083355: _free_r at /home/permal/esp/esp-idf/components/newlib/./syscalls.c:42

0x40193cae: cJSON_free at /home/permal/esp/esp-idf/components/json/library/cJSON.c:82

0x40174785: smooth::core::json::Value::to_string[abi:cxx11]() at /home/permal/code/G2-Alarmsystem/components/Smooth/core/json/Value.cpp:285

0x401206c7: G2Alarm::event(AnalogValue const&) at /home/permal/code/G2-Alarmsystem/components/Smooth/include/smooth/core/ipc/TaskEventQueue.h:90

0x40120878: non-virtual thunk to G2Alarm::event(AnalogValue const&) at ??:?

0x40110809: smooth::core::ipc::TaskEventQueue<AnalogValue>::forward_to_event_queue() at /home/permal/code/G2-Alarmsystem/components/Smooth/include/smooth/core/ipc/TaskEventQueue.h:90

0x4015e7fe: smooth::core::Task::exec() at /home/permal/code/G2-Alarmsystem/components/Smooth/core/Task.cpp:131

0x4015ea0b: smooth::core::Task::start() at /home/permal/code/G2-Alarmsystem/components/Smooth/core/Task.cpp:56

0x4011265c: app_main at /home/permal/code/G2-Alarmsystem/main/./main.cpp:20

0x400d1112: main_task at /home/permal/esp/esp-idf/components/esp32/./cpu_start.c:455

Posted: **Mon Feb 05, 2018 9:02 am**

I saw ESP_Angus reference this thread in this post. After reading that thread, I'm even more certain that there is a bug in the heap corruption code. As such, I've cross posted this as an issue on GitHub.

Posted: **Mon Feb 05, 2018 9:09 am**

Hi permal,

Sorry, I posted the cross-link and then I meant to reply here and got distracted with other tasks and now here we are...

permal wrote:After reading that thread, I'm even more certain that there is a bug in the heap corruption code. As such, I've cross posted this as an issue on GitHub.

There is another common factor between the two of you, which is that you're using cJSON. In the absense of other bug reports this makes me think there is another memory corruption bug in cJSON (or in a common usage pattern of cJSON), but nothing is impossible at this stage.

permal wrote: First question: What fills the memory with 0xfe in the first place?

It gets set inside multi_heap_register(), when the heap is first registered.

permal wrote: And yes, if I don't call cJSON_Print(), I no longer have an issue. However, I can also just not start a task that literally only sleeps in the current use case and the issue also "goes away". I'm not sure what this tells us.

It probably tells us that it's timing related. There's a race between two tasks where one of them is allocating or freeing memory and one of them is reading and then writing an invalid pointer.

Having the additional task in the mix changes the timing a bit and you're all good again - maybe the memory is no longer invalid, or maybe the write lands somewhere in allocated memory and corrupts a buffer which we can't check via heap checking.

The other possibility is simply that allocating the task heap (& TCB structure) changes the heap layout in a way where the invalid write lands in an allocated buffer.

permal wrote: Update:
I'm currently running the exact same code with "Light impact" mode in which the part where it writes the *_FILL_WORD bytes to the buffer is disabled and I'm not getting any issues with destroyed tails.

This may indicate a problem with heap checking, but running the Comprehensive mode also has fairly serious impact on timing (as it has to do a lot of verifying and writing chunks of memory). Given it seems the problem is timing related, that may be why this makes it go away.

The symptom you both have of MALLOC_FILL_WORLD turning up in a "tail" makes me think that something is reading an invalid pointer and then copying that memory to an invalid location (probably an already-freed pointer).

Is there any chance you have a test case firmware that I can compile and run locally?

(Please let me know if I missed any questions in the post above.)

EDIT: Added some details to the reply.

Posted: **Mon Feb 05, 2018 9:35 am**

..memory corruption bug in cJSON (or in a common usage pattern of cJSON)

That is possible, of course. If so, it is still present in 1.7.1 as that is what I'm using. I just remember reading the following in the cJSON readme:

NOTE: ANSI C is not C++ therefore it shouldn't be compiled with a C++ compiler. You can compile it with a C compiler and link it with your C++ code however. Although compiling with a C++ compiler might work, correct behavior is not guaranteed.

Is the ESP build system building cJSON with a C or C++ compiler? Do we know what might break?

Is there any chance you have a test case firmware that I can compile and run locally?

Yes, but it requires IC2 hardware to perform its work (ADS1115 and MCP23017). Without the I2CTask active, the issue doesn't happen. I suppose you could mock the I2C driver so that it gets the analog reads, which eventually ends up transformed into Json-strings via cJSON. I've not tried, but you could possibly mock the I2C task to not read I2C and simply return mocked values. Not sure how that effects timing though; might hide the issue if your theory is correct.

Clone this repo: https://github.com/PerMalmberg/G2-Alarmsystem with its submodules. You'll have to set the clock frequencey, I'm using an ESP32 to it is set to 26Mhz. Possibly also enable comprehensive checks, I can't remember if my commited sdkconfig has that active or not. Wifi-settings are in wifi-creds.h. I'm on IRC as "Yoari" if you want to chat directly, though I might not be available at all times.

The schematics I'm running this on is available here, in KiCad format: https://github.com/PerMalmberg/IO-Card-G2 if that helps you set things up.

Posted: **Tue Feb 06, 2018 2:58 am**

Thank you again ESP_Angus for helping out here and in my thread.

I didn't see the forum notification email for some reason and just spotted your response over on my thread a few minutes ago.

Maybe with two of us now we'll figure out if this is a cJSON issue or something else entirely.

Since my last post I've:

- Added support for Linux to my esp32 application, stubbing out a range of hardware related functions, and testing tons of requests through libesphttpd. Note that I'm using esp-idf daa8cf, which is master from late January and it has cJSON 1.6.0. Ran this under valgrind dozens of times and nothing was detected and the cJSON code was active. Now it wasn't identical data being converted to json but the values were representative and the same code paths were taken. The cJSON, libesphttpd, and the code driving the cJSON is untouched. Good news is that now I can run under Linux for quicker testing of other non-hardware things

- Continued rewriting libesphttpd, haven't found anything yet that has fixed the issue although I've fixed another handful of potential issues.

- Had heap crashes occur at system startup, before any calls to cJSON, and no data to the web server, although based on the trace it may have been during web server initialization but it looks possible it was inside of some wifi init code given the print and knowing the startup sequence:

Code: Select all

W (321) phy_init: failed to load RF calibration data (0xffffffff), falling back to full calibration
I (471) phy: phy_version: 380.0, b77d4dc, Jan 24 2018, 17:42:07, 0, 2
I (481) wifi: mode : sta (30:ae:a4:0c:d4:54)
I (481) CLI: uart init complete
I (481) wifi: milliseconds in state: 200.000000
I (481) wifi: start_STA_connectioCORRUPT HEAP: multi_heap.c:370 detected at 0x3ffe1c24
abort() was called at PC 0x4008a36f on core 1
0x4008a36f: multi_heap_assert at /Users/cmorgan/projects/loadcontrol/esp-idf/components/heap/./multi_heap.c:636
 (inlined by) multi_heap_malloc_impl at /Users/cmorgan/projects/loadcontrol/esp-idf/components/heap/./multi_heap.c:370
...

Added some heap checking calls and it didn't reproduce which points to something potentially timing related.

I'll keep watching here to see what comes out, and of course retest when the updated cJSON lands.

Posted: **Tue Feb 06, 2018 3:04 am**

ESP_Angus, are you still looking for a test build that results in the problem? Would you need source as well? If so I can look to do a build that disables required hardware and try to reproduce.

Posted: **Tue Feb 06, 2018 3:06 am**

NOTE: ANSI C is not C++ therefore it shouldn't be compiled with a C++ compiler. You can compile it with a C compiler and link it with your C++ code however. Although compiling with a C++ compiler might work, correct behavior is not guaranteed.
Is the ESP build system building cJSON with a C or C++ compiler? Do we know what might break?

ESP-IDF build system will use a C compiler.

There are some differences between C & C++ compilers when compiling C, although most of the differences I can think of would mostly result in error/warnings from the C++ compiler. Possibly this is a preempt attempt to avoid bug reports when this happens?

Is there any chance you have a test case firmware that I can compile and run locally?
Yes, but it requires IC2 hardware to perform its work (ADS1115 and MCP23017). Without the I2CTask active, the issue doesn't happen. I suppose you could mock the I2C driver so that it gets the analog reads, which eventually ends up transformed into Json-strings via cJSON. I've not tried, but you could possibly mock the I2C task to not read I2C and simply return mocked values. Not sure how that effects timing though; might hide the issue if your theory is correct.

Unfortunately I'm not able to modify your project myself, but if you have a standalone example that I can run (maybe a modified version of this project with stubbed out hardware, as you mention) then this will certainly help a lot.

I had a quick look in the Value class and noticed what could be some memory safety issues. Value class has the notion of "ownership" about whether or not this particular object can delete cJSON data when it's destroyed. However, a number of class functions (for example operator= & operator[]) call cJSON functions which free data as part of their behaviour (cJSON_ReplaceItem* or cJSON_DeleteItem*). In the case that other references to these cJSON data structures exist, this looks to me like it could cause dangling pointers to freed memory.

I didn't audit thoroughly enough to know if this is really a problem, please take a look and let me know. Perhaps consider having the class create new "owner" objects with cloned cJSON data to return in these cases. Or you could look for a pure C++ JSON library which will be easier to integrate with C++ usage patterns.

As the Value class' only dependency is cJSON, the other thing you could try is writing some test cases and compiling these for Linux, then run it under valgrind. Valgrind can do things which are not feasible within ESP32's resources.

Posted: **Tue Feb 06, 2018 3:08 am**

cmorgan wrote: - Added support for Linux to my esp32 application, stubbing out a range of hardware related functions, and testing tons of requests through libesphttpd. Note that I'm using esp-idf daa8cf, which is master from late January and it has cJSON 1.6.0. Ran this under valgrind dozens of times and nothing was detected and the cJSON code was active. Now it wasn't identical data being converted to json but the values were representative and the same code paths were taken. The cJSON, libesphttpd, and the code driving the cJSON is untouched. Good news is that now I can run under Linux for quicker testing of other non-hardware things

Great to hear. Is the threading of the Linux code similar to the ESP-IDF code (ie number of threads, work done in each thread, etc).

I'll keep watching here to see what comes out, and of course retest when the updated cJSON lands.

Landed overnight:
https://github.com/espressif/esp-idf/co ... b4f110d6ba

Posted: **Tue Feb 06, 2018 3:17 am**

Hi Esp_Angus.

Btw, how does one mention a username to let them see a post? Or is that not possible?

I’ll try tomorrow with the updated cJSON.

It is the same threading approach, the cJSON calls are from the web server thread. In the Linux version I’m lacking the console thread, some temperature retrieval thread, led blinking, WiFi state management and of course anything related to esp32. The fact that I could run tens of thousands of http requests, each of which ran the same cJSON code as on target, was disappointing after the time it took to port but informative.

I’ll place a bet that says that the cJSON change won’t fix the issue based on my valgrind testing. I’m about 80% confident, there are slight data value differences that could have been using slightly different paths in cJSON.

Hope the original poster here can also retest and provide his results.

Posted: **Tue Feb 06, 2018 6:26 am**

Angus,

I have test project for most of my code in the Smooth framework. The one for Json is here: https://github.com/PerMalmberg/Smooth-t ... t_json.cpp.

This project compiles both for ESP and Linux so I’ve run it through Valgrind and have not seen any issues, but I will have another look. Might be a case I’m not covering.

ESP32 Forum

Heap corruption diagnostics causing heap corruption?.

Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.

Re: Heap corruption diagnostics causing heap corruption?.