visionbuf: fix incorrect length passed to munmap #618
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
fixed a bug in VisionBuf::free() where an incorrect length parameter was passed to munmap(), potentially causing memory issues.
In the allocate() method, the length of the memory mapping (mmap_len) was calculated as
this->len + sizeof(uint64_t)
. However, in the free() method, only this->len was used as the length parameter for munmap(), resulting in an incorrect length.