Removed close guards for Element and Type objects
Bug: 28053769 These objects are tiny and unlikely to cause memory issues. In addition, llvm-rs-cc auto-generated code contains such objects, which are not visibible to developers and impossible to manually destroy, leaving distracting warnings in Strict Mode. Test: RsTest with StrictMode on and CTS tests Change-Id: Iec68cca4f1259124b9f503a230c1a28b97ede1f3
This commit is contained in:
@@ -1071,7 +1071,6 @@ public class Element extends BaseObj {
|
||||
mSize += mElements[ct].mSize * mArraySizes[ct];
|
||||
}
|
||||
updateVisibleSubElements();
|
||||
guard.open("destroy");
|
||||
}
|
||||
|
||||
Element(long id, RenderScript rs, DataType dt, DataKind dk, boolean norm, int size) {
|
||||
@@ -1091,7 +1090,6 @@ public class Element extends BaseObj {
|
||||
mKind = dk;
|
||||
mNormalized = norm;
|
||||
mVectorSize = size;
|
||||
guard.open("destroy");
|
||||
}
|
||||
|
||||
Element(long id, RenderScript rs) {
|
||||
|
||||
@@ -227,7 +227,6 @@ public class Type extends BaseObj {
|
||||
|
||||
Type(long id, RenderScript rs) {
|
||||
super(id, rs);
|
||||
guard.open("destroy");
|
||||
}
|
||||
|
||||
@Override
|
||||
|
||||
Reference in New Issue
Block a user