Android: Fix random crash in HW encode accelerator
There are reports of random Chrome crash due to HW encode accelerator on Android. Possible reason may be: currently we'll reset client factory at encoding error and notify client. But before client stops encoding (calling Destroy() here), if there is any pending frame delivered to encoder, it will fail to get the pointer of client factory. Here we try to leave the client factory life managment to client and only notify the encoding error to client in error handling. BUG=676987 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel;master.tryserver.chromium.win:win_optional_gpu_tests_rel Review-Url: https://codereview.chromium.org/2601003002 Cr-Commit-Position: refs/heads/master@{#440864}
Showing
Please register or sign in to comment