tree bf6c5e90fff21e7ca41c4d776790f8acb2d10f1a
parent 13856a05e7e06fae3ed9668de17aa40fdf3aca47
author Jintao_Zhu <jintao.zhu@gm.com> 1541934804 -0800
committer Tom Cherry <tomcherry@google.com> 1542047055 -0800

logd: fix memory leak due to slow reader

Kernel panic - not syncing: Out of memory occurred once after 8 hours
automatic test which cases are about Summary:logd memory leak UTResult
: 1/1

IssueID: 93440

Rootcause: the method "LogTimeEntry::FilterSecondPass"(called inside
"LogBuffer::flushTo") does not check the condition flag
"LogTimeEntry::mRelease" which will be set to true when "logd" begins
to kick off a client when it finding the client is slow-est.
Therefore the client cannot be kicked off and hence the log-element
list becomes longer and longer if the slowest client reading more
slower than the writer writing.

Change-Id: I91a44a393e63b3122c15ce269ee195e0eb4339e8
Solution: add the check.
Test: logd kills slow reader