TPEPlatform/2014-05-22: Difference between revisions

Line 85: Line 85:
** WIP | F+ | D
** WIP | F+ | D
** Problem: Any graphicBuffer lock/unlock in HwcComposer2D will cause the lock failed in ContentClientDoubleBuffered::FinalizeFrame().
** Problem: Any graphicBuffer lock/unlock in HwcComposer2D will cause the lock failed in ContentClientDoubleBuffered::FinalizeFrame().
** I tried to test the gen lock problem on unagi, leo, and flame. unagi and leo are easy to reproduce it if I call lock/unlock often in HwcComposer. Flame is not easy to reproduce this issue, and it seldom uses HwcComposer.
** I tried to test the gen lock problem on unagi, leo, and flame. unagi and leo are easy to reproduce it if I call lock/unlock often in HwcComposer. Flame is not easy to reproduce this issue, and it seldom uses HwcComposer. According to Peter's suggestion, I should figure out why Setting page doesn't use HwcComposer by dumping layer tree.


* {{Bug|1003893}} - crash in imgFrame::~imgFrame()
* {{Bug|1003893}} - crash in imgFrame::~imgFrame()
Confirmed users
645

edits