谨慎使用android.view.SurfaceView.setVisibility方法

本文介绍: 原因就是此方法会导致native的内存暴增，前提条件你使用 surfaceview去绘制一些复杂的3D图形，绘制复杂、业务复杂的场景；setVi si bi li t y 方法会调用 surfaceVie w的updateSur face,而此方法内部就可能会分配大量的native内存。

原因就是此方法会导致native的内存暴增，前提条件你使用surfaceview去绘制一些复杂的3D图形，绘制复杂、业务复杂的场景；
setVi si bi li t y 方法会调用 surfaceVie w的updateSur face,而此方法内部就可能会分配大量的native内存

查看 updateSurface 源码：

 /** @hide */
protected void updateSurface() {
	final boolean formatChanged = mFormat != mRequestedFormat;
    final boolean visibleChanged = mVisible != mRequestedVisible;
    final boolean creating = (mSurfaceControl == null || formatChanged || visibleChanged)
           &amp;&amp; mRequestedVisible;

	.....
	if (creating) {
       viewRoot.createBoundsSurface(mSubLayer);
           mSurfaceSession = new SurfaceSession();
           mDeferredDestroySurfaceControl = mSurfaceControl;

           updateOpaqueFlag();
          final String name = "SurfaceView - " + viewRoot.getTitle().toString();

           mSurfaceControl = new SurfaceControl.Builder(mSurfaceSession)
               .setName(name)
               .setOpaque((mSurfaceFlags &amp; SurfaceControl.OPAQUE) != 0)
               .setBufferSize(mSurfaceWidth, mSurfaceHeight)
               .setFormat(mFormat)
               .setParent(viewRoot.getSurfaceControl())
               .setFlags(mSurfaceFlags)
               .build();
           mBackgroundControl = new SurfaceControl.Builder(mSurfaceSession)
               .setName("Background for -" + name)
               .setOpaque(true)
               .setColorLayer()
               .setParent(mSurfaceControl)
               .build();

       } else if (mSurfaceControl == null) {
          return;
       }
       .....
}

如上函数，重点在于满足 creating为true的情况下new SurfaceControl.Builder，在这个 builder 里面，会直接创建SurfaceControl对象，在SurfaceControl构造方法中有一个：

private SurfaceControl(SurfaceSession session, String name, int w, int h, int format, int flags,
              SurfaceControl parent, SparseIntArray metadata){
	mNativeObject = nativeCreate(session, name, w, h, format, flags,
                      parent != null ? parent.mNativeObject : 0, metaParcel);
}

nativeCreate是一个 native方法，在native层的代码如下：

static jlong nativeCreate(JNIEnv* env, jclass clazz, jobject sessionObj,
        jstring nameStr, jint w, jint h, jint format, jint flags, jlong parentObject,
        jobject metadataParcel) {
    ....
    SurfaceControl *parent = reinterpret_cast<SurfaceControl*>(parentObject);
    sp<SurfaceControl> surface;
    ......
    status_t err = client->createSurfaceChecked(
            String8(name.c_str()), w, h, format, &amp;surface, flags, parent, std::move(metadata));
   .....
    return reinterpret_cast<jlong>(surface.get());
}

status_t SurfaceComposerClient::createSurfaceChecked(const String8&amp; name, uint32_t w, uint32_t h,
                                                     PixelFormat format,
                                                     sp<SurfaceControl>* outSurface, uint32_t flags,
                                                     SurfaceControl* parent,
                                                     LayerMetadata metadata) {
    sp<SurfaceControl> sur;
    status_t err = mStatus;
	if (mStatus == NO_ERROR) {
	       sp<IBinder> handle;
	       sp<IBinder> parentHandle;
	       sp<IGraphicBufferProducer> gbp;
	
	       if (parent != nullptr) {
	           parentHandle = parent->getHandle();
	       }
        err = mClient->createSurface(name, w, h, format, flags, parentHandle, std::move(metadata),
                                     &amp;handle, &amp;gbp);
        .....
    }
    return err;
}

到这里就不继续往下分析，不过也不难看出就是要重新创建一个 surface，上面的createSurfaceChec ked方法中的“IGrap hicBuf ferProducer”代码就是分配对应的图像内存的例证；所以从上surfaceView的setVisi bi lity方法很有可能就在native层分配内存，如果频繁调用setVisi bi lity方法，而又没做好回收工作，就极有可能使内存暴增，系统和应用奔溃，出现 android.view.Surface$OutOfResourcesExc ept ion 异常