CCExtractor Development
Memory leak diagnostics
There may be a few places in the code where we do not explicitly free dynamically allocated memory that is no longer needed. The job here is to test for such instances using valgrind, and wherever applicable, fix the memory leak by freeing the allocated memory.
Task tags
Students who completed this task
Evgeny Shulgin
Task type
- code Code
- done_all Quality Assurance