Firmware structure: risk of memory leaks/fragmentation ?

Controllers Smoothie
1

Hi all,

I am analyzing with much interest smoothie firmware, especially appreciating the modular approach. As I am an old-school C embedded firmware programmer, my question is: due to continuously (re)newed objects (Gcode messages, strdup calls etc) is there any serious risk of memory leaks or memory fragmentation (which would be lethal, as we don’t have garbage collection) ?
A system running smoothie, in my opinion, cannot tolerate such inconveniences, must be up H24
Thanks, regards

Imported from wikidot

2

Hey !

This has been tested a lot and the way it’s done now is fine.
There is a refactor ( we call it the queue refactor ) that will remove most of those new() calls, but we are not there yet.

Cheers :slight_smile: