Optimise the sourcecode to have as little leaks as possible and free up memory [valgring] #9

New Issue

_N0x · 2022-02-20T01:06:36+01:00

_N0x commented

2022-02-20 01:06:36 +01:00

Optimise the source code as neatly as possible (see valgrind --leak-check=yes --track-origins=yes)
Better naming system for variables
Use the same coding style everywhere (make use of clang-format)

* Optimise the source code as neatly as possible (see `valgrind --leak-check=yes --track-origins=yes`) * Better naming system for variables * Use the same coding style everywhere (make use of `clang-format`)

_N0x changed title from ~~Optimise the sourcecode to have as little leaks as possible and free up memory [valgrin~~ to Optimise the sourcecode to have as little leaks as possible and free up memory [valgring]

2022-02-20 01:07:25 +01:00

_N0x added the

enhancement

label 2022-02-20 01:07:31 +01:00

_N0x added this to the 0.2 - Programm has been tested and optimized milestone 2022-02-20 01:07:35 +01:00

_N0x commented

2022-02-20 01:40:28 +01:00

A big focus should also be put on how to to free up cJSON data structures since those are causing almost all leaks currently within the code

Sign in to join this conversation.