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

Open
opened 2 years ago by _N0x · 1 comments
_N0x commented 2 years ago
Owner
  • 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] 2 years ago
_N0x added the
enhancement
label 2 years ago
_N0x added this to the 0.2 - Programm has been tested and optimized milestone 2 years ago
_N0x commented 2 years ago
Poster
Owner

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

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.
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: _N0x/f8prog#9
Loading…
There is no content yet.