History log of /frameworks/base/tests/HwAccelerationTest/src/com/android/test/hwui/PathDestructionActivity.java
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
b192344234dcee215462e6218cf1c4384b9916f1 02-Mar-2017 Narayan Kamath <narayan@google.com> MathUtils: Remove static Random field.

This is unsafe because the random will be seeded in the zygote, which
means all processes on the system generate the same sequence of random
numbers. Fortunately, this code is only used in tests, so get rid of it.

Note that the Random that backs Math.random() is reseeded after every
fork to avoid a similar issue.

Bug: 35918685
Test: HwAccelerationTest
Change-Id: Ice79aa25bb9017f7a0b91659afe04112850cb74b
/frameworks/base/tests/HwAccelerationTest/src/com/android/test/hwui/PathDestructionActivity.java
d34dd71800d9a1077e58c3b7f2511c46848da417 03-May-2012 Chet Haase <chet@google.com> Fix hang/crash in native path code

An optimization for paths is to only create a texture for the original native
Path object, and have all copies of that object use that texture. This works in
most cases, but sometimes that original path object may get destroyed (when the
SDK path object is finalized) while we are still referencing and using that object
in the DisplayList code. This causes undefined errors such as crashes and hanging
as we iterate through the operations of a destroyed (and garbage-filled) path object.

The fix is to use the existing ResourceCache to refcount the original path until
we are done with it.

Issue #6414050 Analytics Dogfood App crashes reliably on Jellybean

Change-Id: I5dbec5c069f7d6a1e68c13424f454976a7d188e9
/frameworks/base/tests/HwAccelerationTest/src/com/android/test/hwui/PathDestructionActivity.java