2017-03-23 36 views
1

上下文時手動創建連接到GLContext默認SurfaceTexture?如果是這樣,怎麼樣?GLConsumer已連接到新的表面紋理

下面是一個例子,我想創建自己的SurfaceTexture並將其設置爲TextureView

public class MainActivity extends AppCompatActivity { 
    @Override 
    protected void onCreate(Bundle savedInstanceState) { 
     super.onCreate(savedInstanceState); 
     setContentView(R.layout.activity_main); 

     TextView textView = (TextView) findViewById(R.id.version); 
     TextureView textureView = (TextureView) findViewById(R.id.texture); 

     int[] arr = new int[1]; 
     GLES20.glGenTextures(1, arr, 0); 
     int texName = arr[1]; 

     SurfaceTexture surfaceTexture = new SurfaceTexture(texName); 
     textureView.setSurfaceTexture(surfaceTexture); 
    } 
} 

我經常收到:

E/GLConsumer:[unnamed- 29058-0] attachToContext:GLConsumer已經連接

並且例外:

E/AndroidRuntime:致命異常:主 工藝:com.example.dkarmazin.openglesversion,PID:29058 了java.lang.RuntimeException:錯誤attachToGLContext期間(詳見logcat的 ) 在 機器人。 graphics.SurfaceTexture.attachToGLContext(SurfaceTexture.java:215) 在 android.view.GLES20TextureLayer.setSurfaceTexture(GLES20TextureLayer.java:86) 在 android.view.HardwareRenderer $ Gl20Renderer.setSurfaceTexture(HardwareRenderer.java:2 228.) at android.view.TextureView.getHardwareLayer(TextureView.java:401) at android.view.View.getDisplayList(View.java:13443) at android.view.View.getDisplayList(View.java:13519) 在android.view.View.draw(View.java:14297) 在android.view.ViewGroup.drawChild(ViewGroup.java:3115) 在android.view.ViewGroup.dispatchDraw(ViewGroup.java:2952) 在android.view.View.getDisplayList(View.java:13472) 在android.view.View.getDisplayList(View.java:13519) 在android.view.View.draw(View.java:14297) 在android.view.ViewGroup.drawChild(ViewGroup.java:3115) 在android.view.ViewGroup.dispatchDraw(ViewGroup.java:2952) 在android.view.View.draw(View.java:14583) 在android.widget.FrameLayout.draw(FrameLayout.java:472) 在android.view.View.getDisplayList(View.java:13477) 在android.view.View.getDisplayList(View.java:13519) 在機器人。 view.draw.View(View.java:14297) at android.view.ViewGroup.drawChild(ViewGroup.java:3115) at android.view.ViewGroup.dispatchDraw(ViewGroup.java:2952) (android.view.java:14583) at android.support.v7.widget.ActionBarOverlayLayout.draw(ActionBarOverlayLayout.java:444) at android.view.View.getDisplayList(View.java: (ViewGroup.java:3115)在android.view.View.getDisplayList(View.java:13519) at android.view.View.draw(View.java:14297) at android.view.ViewGroup.drawChild(ViewGroup.java:3115) 在android.view。ViewGroup.dispatchDraw(ViewGroup.java:2952) at android.view.View.getDisplayList(View.java:13472) at android.view.View.getDisplayList(View.java:13519) at android.view.View。繪製(View.java:14297) 在android.view.ViewGroup.drawChild(ViewGroup.java:3115) 在android.view.ViewGroup.dispatchDraw(ViewGroup.java:2952) 在android.view.View.getDisplayList( (View.java:13472) at android.view.View.getDisplayList(View.java:13519) at android.view.View.draw(View.java:14297) at android.view.ViewGroup.drawChild(ViewGroup。的java:3115) 在android.view.ViewGroup.dispatchDraw(ViewGroup.java:2952) 在android.view.View.draw(View.java:14583) 在android.widget.FrameLayout.draw(FrameLayout.java:在android.view.View.getDisplayList(View.java:13477) at android.view.View() .getDisplayList(View.java:13519) at android.view.HardwareRenderer $ GlRenderer.buildDisplayList(HardwareRenderer.java:1577) at android.v iew.HardwareRenderer $ GlRenderer.draw(HardwareRenderer.java:1449) 在android.view.ViewRootImpl.draw(ViewRootImpl.java:2530) 在android.view.ViewRootImpl.performDraw(ViewRootImpl.java:2402) 的機器人。 view.ViewRootImpl.performTraversals(ViewRootImpl.java:2019) 在android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1079) 在 android.view.ViewRootImpl $ TraversalRunnable.run(ViewRootImpl.java:5948) 在 android.view.Choreographer $ CallbackRecord.run(Choreographer.java:761) at android.view.Choreographer.doCallbacks(Choreographer.java:574) at android.view.Choreographer.doFrame(Choreographer.java:544) at android.view.Choreographer $ FrameDisplayEventReceiver.run(Choreographer.java:747) at android.os.Handler.handleCallback(Handler.java:733 ) at android.os.Handler.dispatchMessage(Handler.java:95) at android.os.Looper.loop(Looper.java:136) at android.app.ActivityThread.main(ActivityThread.java:5102) 在java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:515) at com.android.internal.os.ZygoteInit $ MethodAndArgsCaller.run(ZygoteInit.java:785) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:601) at dalvik.system.NativeStart.main (本機方法)

調用新創建SurfaceTexture對象detachFromGLContext解決了這個問題,但是這是相當混亂,因爲我可以證實,attachToGLContext永遠不會在這種情況下調用。

P.S.我知道TextureView默認有它自己的SurfaceTexture。在這種情況下,我必須使用從SurfaceTexture延伸的自己的實現。

回答

1

我會發佈一個答案,以防萬一別人面臨同樣的問題。

據推測,新的表面紋理連接到GLContext默認情況下是由於:

  1. 表面紋理構造函數調用nativeInit

  2. nativeInit對應SurfaceTexture_init:https://android.googlesource.com/platform/frameworks/base.git/+/android-4.4.4_r2.0.1/core/jni/android/graphics/SurfaceTexture.cpp#337

  3. SurfaceTexture_init創建一個新的GLConsumer here:https://android.googlesource.com/platform/frameworks/base.git/+/android-4.4.4_r2.0.1/core/jni/android/graphics/SurfaceTexture.cpp#239

解決方法是在調用超級構造函數後,從GLContext手動分離新創建的SurfaceTexture 。

public class MySurfaceTexture extends SurfaceTexture { 
    public MySurfaceTexture(int texName) { 
     super(texName); 
     init(); 
    } 

    private void init() { 
     super.detachFromGLContext(); 
    } 
} 

我擡頭文檔專門爲API-19,但你可以按照其他API級別相同的路徑。

1

在Android O中有一個new constructor,它不會立即附加。聽起來就像你想要的那樣。正如你的自我回答所言,先前的構造函數會自動附加到當前線程的GL上下文。