NRF52840_DK - Operator new[] out of memory

[j3hill]

This example builds with storage type TDB_EXTERNAL without errors, but reboots in a loop due to a fatal error ("Operator new[] out of memory") when run.
Example version: mbed-os-5.11.0-rc2 - d9625811c9193ac3ab36a969bab93e28dac03776
OS: Windows 10
Compiler: GCC_ARM
Board: NRF52840_DK

Test output:

--- Mbed OS KVStore static API example ---
kv_reset
kv_reset -> 271
kv_set first dummy key
kv_set -> 271
kv_get_info of first key
kv_get_info -> 271
kv_get_info key: /kv/dummy_key1
kv_get_info info - size: 1879048192, flags: 536889856
kv_get first key


++ MbedOS Error Info ++
Error Status: 0x8001011F Code: 287 Module: 1
Error Message: Operator new[] out of memory

Location: 0x352C1
Error Value: 0x70000001
Current Thread: main  Id: 0x2000577C Entry: 0x35829 StackSize: 0x1000 StackMem: 0x200057C0 SP: 0x200066A8
For more info, visit: https://armmbed.github.io/mbedos-error/?error=0x8001011F
-- MbedOS Error Info --

== The system has been rebooted due to a fatal error. ==

[adbridge]

@dannybenor @offirko please take a look

[dannybenor]

I think I added a comment here. It works only on targets that have spif component as explained in the Readme. K64f

[adbridge]

@dannybenor Even if that is the case , surely we should not be getting fatal errors?! Unsupported features/targets should fail during compilation with a suitable warning / error ? cc @ARMmbed/mbed-os-core

[deepikabhavnani]

make sure the target.json for the target includes the "components": ["FLASHIAP"] and device_has": ["FLASH"] or add this section to the example mbed_app.json.

Even if that is the case , surely we should not be getting fatal errors?

Please add #error in example if DEVICE_FLASHIAP and DEVICE_FLASH are not set. Error with proper message and explanation is except able

[deepikabhavnani]

https://github.com/ARMmbed/mbed-os/blob/0283bb84e469c75ebf8ded601312332ac099c633/features/storage/kvstore/mbed_lib.json

KVStore disables feature for few targets and tests check for #if !KVSTORE_ENABLED. Same can be done for example, after setting enabled: false for this target.

[ciarmcom]

@j3hill thank you for raising this issue.Please take a look at the following comments:

Could you add some more detail to the description? A good description should be at least 25 words.
What target(s) are you using?
What toolchain(s) are you using?
What version of Mbed OS are you using (tag or sha)?
It would help if you could also specify the versions of any tools you are using?
How can we reproduce your issue?

NOTE: If there are fields which are not applicable then please just add 'n/a' or 'None'.This indicates to us that at least all the fields have been considered.
Please update the issue header with the missing information, the issue will not be mirroredto our internal defect tracking system or investigated until this has been fully resolved.

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

@j3hill it has been 5 days since the last reminder. Could you please update the issue header as previously requested?

[ciarmcom]

Thank you for raising this detailed GitHub issue. I am now notifying our internal issue triagers.
Internal Jira reference: https://jira.arm.com/browse/IOTOSM-3104