You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Valgrind inspection revealed memory leaks in the original code, with
43,632 bytes lost across 909 blocks per test. Analysis showed that the
initialization function was being called repeatedly within the testing
loop, each time reallocating the context array without any provision to
free prior memory allocations. This uncontrolled repetition caused
memory to accumulate not freed over multiple test iterations, leading to
the observed leaks. To correct this, the initialization process was
revised to execute only once before testing begins, and a cleanup was
added to release all allocated memory when testing concludes. To further
prevent memory-related issues, the measurement function was updated to
check all memory allocations, ensuring robustness against potential
failures.
Change-Id: Ia2639595a1015f792f1614e0771a6300ddaa22ff
0 commit comments