5 years, 6 months ago.

Memory problems after updating from 3.2.0 RC7 to 3.2.0 Stable

Hello,

I updated the xDot library from 3.2.0 RC7 to the 3.2.0 stable version and now I have memory problems. I am using a thread with a stack size of 1024 bytes in my project. After updating, I don't have enough memory to create this thread. After investigating, I noticed the library creates a new application_unnamed_thread with a stack size of 2560 bytes. See the memory information below:

Before upgrading:

Quote:

Thread: 0x2000267C, Stack size: 1496 / 2048 Thread: 0x200012B8, Stack size: 88 / 512 Thread: 0x200039B4, Stack size: 1128 / 2048 Thread: 0x20001274, Stack size: 104 / 768 Heap size: 15760 / 21312 bytes

ID: 0x2000267c Name: main State: 2 Priority: 24 Stack Size: 2048 Stack Space: 552

ID: 0x200012b8 Name: rtx_idle State: 1 Priority: 1 Stack Size: 512 Stack Space: 424

ID: 0x200039b4 Name: application_unnamed_thread State: 3 Priority: 32 Stack Size: 2048 Stack Space: 920

ID: 0x20001274 Name: rtx_timer State: 3 Priority: 40 Stack Size: 768 Stack Space: 664

After upgrading:

Quote:

Thread: 0x20002684, Stack size: 1496 / 2048 Thread: 0x200012B8, Stack size: 88 / 512 Thread: 0x200039BC, Stack size: 136 / 2048 Thread: 0x20001274, Stack size: 104 / 768 Thread: 0x20003C6C, Stack size: 1104 / 2560 Heap size: 16600 / 21304 bytes

ID: 0x20002684 Name: main State: 2 Priority: 24 Stack Size: 2048 Stack Space: 552

ID: 0x200012b8 Name: rtx_idle State: 1 Priority: 1 Stack Size: 512 Stack Space: 424

ID: 0x200039bc Name: application_unnamed_thread State: 3 Priority: 32 Stack Size: 2048 Stack Space: 1912

ID: 0x20001274 Name: rtx_timer State: 3 Priority: 40 Stack Size: 768 Stack Space: 664

ID: 0x20003c6c Name: application_unnamed_thread State: 3 Priority: 32 Stack Size: 2560 Stack Space: 1456

What is the function of this, and the other running application_unnamed_thread, and is it possible to stop these or decrease their stack size?

Greetings, Terry

Question relating to:

MultiTech's official mbed team.
Be the first to answer this question.