[
https://issues.apache.org/jira/browse/TS-3754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629091#comment-14629091
]
Oknet Xu commented on TS-3754:
------------------------------
it is not easy to trigger the bug as your said the method 'set' only used in
two place.
the manager proc restart it after core dumped.
it is non repeatable scene, random condition.
the cache data do not has a data verify mechanism.
maybe someone already create an issue and post backstrace and log output.
> IOBuffer memory leak
> --------------------
>
> Key: TS-3754
> URL: https://issues.apache.org/jira/browse/TS-3754
> Project: Traffic Server
> Issue Type: Bug
> Components: Core
> Reporter: Oknet Xu
> Assignee: Alan M. Carroll
> Priority: Critical
> Fix For: 6.1.0
>
>
> the pointer `_end_buf` exceed the IOBufferData->_data size if offset > 0
> patch at below
> {code}
> diff --git a/iocore/eventsystem/P_IOBuffer.h b/iocore/eventsystem/P_IOBuffer.h
> index 3b8c323..71de17d 100644
> --- a/iocore/eventsystem/P_IOBuffer.h
> +++ b/iocore/eventsystem/P_IOBuffer.h
> @@ -477,7 +477,7 @@ IOBufferBlock::set(IOBufferData *d, int64_t len, int64_t
> offset)
> data = d;
> _start = buf() + offset;
> _end = _start + len;
> - _buf_end = _start + d->block_size();
> + _buf_end = buf() + d->block_size();
> }
>
> TS_INLINE void
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
