[ Cherry-pick of http://ag/34331848 ]
[ Merge of http://go/wvgerrit/224951 ]
There was a potential dangling pointer issue that was enabled
by how CdmInfo is initilized. The file system that was passed
into the CdmEngine instance was pointing to a location in memory
that was not stable between move operations in the CdmInfo.
See b/429054262 for memory diagram of issue.
The CdmInfo is a private class within the Android CDM class, which
restricts the potential operations on it. The easiest solution
is wrap the file system in a unique pointer; ensuring the pointer
remains stable even if a particular data segment of CdmInfo is
moved.
The default constructor for CdmInfo is deleted; this will force the
compiler to fail if |cdms_| is used in ways that would result in
uninitialized pointers.
Bug: 429054262
Test: WvTs on Komodo
Change-Id: I76a49fc5181ebd1613e238aa49986083a9f397ec
(cherry picked from commit 4c105faa4923bd9bd6352f757dedf3eaf9ed88fd)
d7eab65c8c