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
Add a benchmark test to ensure that changes to the codebase do not introduce memory leaks.
Why
We found several memory leaks in the past releases (#1431, #1488, and #1493). These issues could have quite easily been spotted earlier and fixed quickly, avoiding several days worth of debugging and profiling. To mitigate the risk of this occurring again we want to create a benchmark test that will ensure that the memory usage stays constant between changes to the codebase.
The text was updated successfully, but these errors were encountered:
What
Add a benchmark test to ensure that changes to the codebase do not introduce memory leaks.
Why
We found several memory leaks in the past releases (#1431, #1488, and #1493). These issues could have quite easily been spotted earlier and fixed quickly, avoiding several days worth of debugging and profiling. To mitigate the risk of this occurring again we want to create a benchmark test that will ensure that the memory usage stays constant between changes to the codebase.
The text was updated successfully, but these errors were encountered: