Possible Ring Buffer Fix #586
Avoid memory leak if passed data is greater than maximum allowed size and overwriteOld iset set to true.
After talk about this PR: There will be an update to this PR where the function will actually cut off the tail of a packet which is too large and write the remaining packet size (maximum ring buffer size) into the ring buffer if
overwriteOld is set to true.
During implementation of the updated functionality for the
overwriteOld flag, it showed that the
overwriteOld flag might not be handled correctly in some cases.
Setting this PR to WIP until I figure it out.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?