718ac2c814477c3a90821d2d10f71b256c775930
The following sequence of events would lead to a crash: - Reader A is created. - Reader A produces a frame (A0) - Texture is resized. - Reader B is created and reader A is scheduled to be closed. - Reader A produces a frame (A1). This is skipped. - Reader A is closed. - Frame A0 is acquired. Because we closed Reader A the frame A0 is invalid. The fix is to not close Reader A when it is the last reader to produce a frame. Fixes internal bug b/318458306
Description
Languages
Dart
75.4%
C++
16.4%
Objective-C++
2.7%
Java
2.7%
Objective-C
0.6%
Other
1.8%