• State Not Answered
  • Replies 10 replies
  • Subscribers 65 subscribers
  • Views 253 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 326080
Options

Memory allocation

NilsDR

Hi

I'm trying to figure out how to manage my memory on the nrf9160 sip. Currently my application crashes on a specific lines where I try to allocate a large C++ string (the crash happens at around a string size of 10 kB see call stack below).  

I've tried playing around with the config file and use different sizes, but nothing seems to help.

# Heap and stacks
CONFIG_HEAP_MEM_POOL_SIZE=32000
CONFIG_MAIN_STACK_SIZE=32000
CONFIG_SYSTEM_WORKQUEUE_STACK_SIZE=32000

I can see when I'm building my application I get this memory report, which also indicates that I lots of unused memory:

I also found the thread analyzer function to print out the stack usage of all threads, which reports runtime that there is lots of memory left:

[00:04:20.621,856] <inf> thread_analyzer: Thread analyze:
[00:04:20.622,406] <inf> thread_analyzer:  0x20011310          : STACK: unused 496 usage 272 / 768 (35 %); CPU: 0 %
[00:04:20.623,046] <inf> thread_analyzer:       : Total CPU cycles used: 51217
[00:04:20.623,718] <inf> thread_analyzer:  0x200113b8          : STACK: unused 848 usage 176 / 1024 (17 %); CPU: 0 %
[00:04:20.624,389] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:04:20.628,845] <inf> thread_analyzer:  0x20011660          : STACK: unused 31368 usage 752 / 32120 (2 %); CPU: 0 %
[00:04:20.629,547] <inf> thread_analyzer:       : Total CPU cycles used: 1188
[00:04:20.630,126] <inf> thread_analyzer:  0x200114b0          : STACK: unused 236 usage 84 / 320 (26 %); CPU: 58 %
[00:04:20.630,767] <inf> thread_analyzer:       : Total CPU cycles used: 4950365
[00:04:20.634,155] <inf> thread_analyzer:  0x20011558          : STACK: unused 22480 usage 9640 / 32120 (30 %); CPU: 41 %
[00:04:20.634,857] <inf> thread_analyzer:       : Total CPU cycles used: 3513906
[00:04:20.635,559] <inf> thread_analyzer:  ISR0                : STACK: unused 1672 usage 376 / 2048 (18 %)

I do not use dynamic allocation (or atleast not that I'm aware of) so the heap should be unsed.

Is this a memory issue? And is there any way to get more information about my memory usage runtime?

  • 0

    Hello,

    Could you please share the string allocation part from your code? 

    Thanks.

    BR
    Kazi 

  • 0 in reply to Kazi Afroza Sultana

    I've made this small test sample: 

    int main(void)
{	
	std::string test;

	thread_analyzer_print();

	for(int i = 0; i < 10000; i++)
	{
		test += std::to_string(i);

		if(i % 1000 == 0)
			thread_analyzer_print();

		k_sleep(K_MSEC(10));
	}

	return 0;
}

    The memory prints doesn't show a increase in usage when I concatenate to the string. If it is not allocated on the main stack, then where is it allocated? 

    [00:00:00.380,676] <inf> thread_analyzer: Thread analyze:
[00:00:00.387,268] <inf> thread_analyzer:  mqtt_helper_thread  : STACK: unused 2528 usage 32 / 2560 (1 %); CPU: 0 %
[00:00:00.398,925] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.406,951] <inf> thread_analyzer:  0x2000d308          : STACK: unused 992 usage 32 / 1024 (3 %); CPU: 0 %
[00:00:00.418,487] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.427,337] <inf> thread_analyzer:  sysworkq            : STACK: unused 7800 usage 200 / 8000 (2 %); CPU: 0 %
[00:00:00.439,056] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.446,960] <inf> thread_analyzer:  idle                : STACK: unused 288 usage 32 / 320 (10 %); CPU: 0 %
[00:00:00.458,496] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.482,208] <inf> thread_analyzer:  main                : STACK: unused 124592 usage 944 / 125536 (0 %); CPU: 100 %
[00:00:00.494,506] <inf> thread_analyzer:       : Total CPU cycles used: 3519
[00:00:00.502,838] <inf> thread_analyzer:  ISR0                : STACK: unused 1624 usage 424 / 2048 (20 %)
[00:00:00.513,732] <inf> thread_analyzer: Thread analyze:
[00:00:00.520,324] <inf> thread_analyzer:  mqtt_helper_thread  : STACK: unused 2528 usage 32 / 2560 (1 %); CPU: 0 %
[00:00:00.531,982] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.540,008] <inf> thread_analyzer:  0x2000d308          : STACK: unused 992 usage 32 / 1024 (3 %); CPU: 0 %
[00:00:00.551,544] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.560,363] <inf> thread_analyzer:  sysworkq            : STACK: unused 7800 usage 200 / 8000 (2 %); CPU: 0 %
[00:00:00.572,113] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.579,986] <inf> thread_analyzer:  idle                : STACK: unused 288 usage 32 / 320 (10 %); CPU: 0 %
[00:00:00.591,552] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:00.615,295] <inf> thread_analyzer:  main                : STACK: unused 124592 usage 944 / 125536 (0 %); CPU: 100 %
[00:00:00.627,563] <inf> thread_analyzer:       : Total CPU cycles used: 7880
[00:00:00.635,894] <inf> thread_analyzer:  ISR0                : STACK: unused 1624 usage 424 / 2048 (20 %)
[00:00:10.748,352] <inf> thread_analyzer: Thread analyze:
[00:00:10.754,943] <inf> thread_analyzer:  mqtt_helper_thread  : STACK: unused 2368 usage 192 / 2560 (7 %); CPU: 0 %
[00:00:10.766,662] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:10.774,658] <inf> thread_analyzer:  0x2000d308          : STACK: unused 824 usage 200 / 1024 (19 %); CPU: 0 %
[00:00:10.786,407] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:10.795,257] <inf> thread_analyzer:  sysworkq            : STACK: unused 7800 usage 200 / 8000 (2 %); CPU: 0 %
[00:00:10.807,006] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:10.814,880] <inf> thread_analyzer:  idle                : STACK: unused 236 usage 84 / 320 (26 %); CPU: 96 %
[00:00:10.826,538] <inf> thread_analyzer:       : Total CPU cycles used: 329007
[00:00:10.850,738] <inf> thread_analyzer:  main                : STACK: unused 124592 usage 944 / 125536 (0 %); CPU: 3 %
[00:00:10.862,884] <inf> thread_analyzer:       : Total CPU cycles used: 13279
[00:00:10.871,276] <inf> thread_analyzer:  ISR0                : STACK: unused 1624 usage 424 / 2048 (20 %)
[00:00:20.983,581] <inf> thread_analyzer: Thread analyze:
[00:00:20.990,173] <inf> thread_analyzer:  mqtt_helper_thread  : STACK: unused 2368 usage 192 / 2560 (7 %); CPU: 0 %
[00:00:21.001,892] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:21.009,887] <inf> thread_analyzer:  0x2000d308          : STACK: unused 824 usage 200 / 1024 (19 %); CPU: 0 %
[00:00:21.021,636] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:21.030,487] <inf> thread_analyzer:  sysworkq            : STACK: unused 7800 usage 200 / 8000 (2 %); CPU: 0 %
[00:00:21.042,205] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:21.050,109] <inf> thread_analyzer:  idle                : STACK: unused 236 usage 84 / 320 (26 %); CPU: 97 %
[00:00:21.061,737] <inf> thread_analyzer:       : Total CPU cycles used: 658007
[00:00:21.085,937] <inf> thread_analyzer:  main                : STACK: unused 124592 usage 944 / 125536 (0 %); CPU: 2 %
[00:00:21.098,052] <inf> thread_analyzer:       : Total CPU cycles used: 18668
[00:00:21.106,445] <inf> thread_analyzer:  ISR0                : STACK: unused 1624 usage 424 / 2048 (20 %)
[00:00:31.218,780] <inf> thread_analyzer: Thread analyze:
[00:00:31.225,372] <inf> thread_analyzer:  mqtt_helper_thread  : STACK: unused 2368 usage 192 / 2560 (7 %); CPU: 0 %
[00:00:31.237,091] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:31.245,086] <inf> thread_analyzer:  0x2000d308          : STACK: unused 824 usage 200 / 1024 (19 %); CPU: 0 %
[00:00:31.256,835] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:31.265,655] <inf> thread_analyzer:  sysworkq            : STACK: unused 7800 usage 200 / 8000 (2 %); CPU: 0 %
[00:00:31.277,404] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:31.285,278] <inf> thread_analyzer:  idle                : STACK: unused 236 usage 84 / 320 (26 %); CPU: 97 %
[00:00:31.296,905] <inf> thread_analyzer:       : Total CPU cycles used: 987008
[00:00:31.321,105] <inf> thread_analyzer:  main                : STACK: unused 124592 usage 944 / 125536 (0 %); CPU: 2 %
[00:00:31.333,221] <inf> thread_analyzer:       : Total CPU cycles used: 24055
[00:00:31.341,644] <inf> thread_analyzer:  ISR0                : STACK: unused 1624 usage 424 / 2048 (20 %)
[00:00:41.453,887] <inf> thread_analyzer: Thread analyze:
[00:00:41.460,479] <inf> thread_analyzer:  mqtt_helper_thread  : STACK: unused 2368 usage 192 / 2560 (7 %); CPU: 0 %
[00:00:41.472,198] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:41.480,224] <inf> thread_analyzer:  0x2000d308          : STACK: unused 824 usage 200 / 1024 (19 %); CPU: 0 %
[00:00:41.491,943] <inf> thread_analyzer:       : Total CPU cycles used: 1
[00:00:41.500,793] <inf> thread_analyzer:  sysworkq            : STACK: unused 7800 usage 200 / 8000 (2 %); CPU: 0 %
[00:00:41.512,542] <inf> thread_analyzer:       : Total CPU cycles used: 0
[00:00:41.520,416] <inf> thread_analyzer:  idle                : STACK: unused 236 usage 84 / 320 (26 %); CPU: 97 %
[00:00:41.532,043] <inf> thread_analyzer:       : Total CPU cycles used: 1316009
[00:00:41.556,335] <inf> thread_analyzer:  main                : STACK: unused 124592 usage 944 / 125536 (0 %); CPU: 2 %
[00:00:41.568,450] <inf> thread_analyzer:       : Total CPU cycles used: 29443
[00:00:41.576,873] <inf> thread_analyzer:  ISR0                : STACK: unused 1624 usage 424 / 2048 (20 %)

    After 5000 iterations the program crashes with the same stack trace. Still seems like an allocation problem.

  • 0 in reply to NilsDR

    I read a little more into it and it seems like the std::string is allocating on the heap as it uses the c++ "new" keyword. So maybe a solution is to just configure the heap size to be larger. It doesn't seem like its using the heap defined with CONFIG_HEAP_MEM_POOL_SIZE though. Is there anyway to tell the processor to allocate to the heap defined by the CONFIG_HEAP_MEM_POOL_SIZE?

  • 0

    Hello Nils,

    I have been looking into the issue. I will reply you soon.

  • 0 in reply to NilsDR

    Hello, 

    You may try to set CONFIG_COMMON_LIBC_MALLOC_ARENA_SIZE?

Related