Vscode, nano, mousepad, and sometimes LibreOffice Writer when I've just re-installed the OS to get rid of a years worth of crud and on the fly trying stuff and forget to click "open with" the first time I click on a file. Mainly vscode, however sometimes nano/mousepad are good enough for a quick 1 ...

Yes it does. But it should be noted that its the temp of the chip its self, not an ambient/air temp sensor.

I had the same thoughts when I first started programming using vscode/c/espressif (complete newbie).

For the tools themselves, you don't actually refer to them by location... following the "getting started" you clone the esp-isd then install.sh and then run the export.sh every subsequent time you ...

Did you run the install.sh at least once before running the export.sh?

The install creates a /home/user/.espressif directory by default.

Another thing to consider is that you need python installed in to the OS (1) for it to then install a venv environment within the /home/user/.espressif/python ...

If you are only using vscode for esp-idf stuff then I've found that the quickest way to resolve any issues is to completely delete vscode and its data stores.

In linux those are .vscode/ and .config/Code/ under the /home/your_user/ directory. Deleting those directories completely nukes the vscode ...

That's my guess too.

Thanks for that. Sets my mind more at ease.

Some more information...

I noticed that the "odd" allocations of memory would seemingly move location if I changed the order of the tests so initially I assumed it was possibly something to do with the "chip" loading/caching parts of my program but for the life of me I could not figure out why no ...

In the included stack heap trace created using heap_trace_start(HEAP_TRACE_ALL), heap_trace_stop(), and heap_trace_dump() I have noticed some strange allocations.

The start/stop/dump are around each test (in startUp and tearDown).

I also use of heap_caps_get_free_size(MALLOC_CAP_32BIT | MALLOC_CAP ...

I'm currently playing around with component development.

Within my .code-workspace file I have the following:
"folders": [
{
"name": "test-apps/i2c-mcp9808",
"path": "./test-apps/i2c-mcp9808"
},
{
"name": "ComponentTests",
"path": "./components/i2c-mcp9808/test"
},
{
"name": "examples ...

I'm fairly sure that you will get a different version of the python environment for each version of ESP-IDF in vscode.

And as as far as the tools (compilers/debugger/etc.) are concerned it may re-use some of them and/or create versions in the subdirectories under each tool such as .espressif ...