gecko-dev/widget/android/bindings/SurfaceTexture-classes.txt

[android.graphics.SurfaceTexture = exceptionMode:nsresult]
[android.view.Surface = exceptionMode:nsresult]
<init>(Landroid/view/SurfaceControl;)V = stubName:FromSurfaceControl, exceptionMode:abort
[android.view.SurfaceControl = exceptionMode:nsresult]
isValid()Z = exceptionMode:abort
Bug 1352177 - 3. Update existing binding config files; r=snorp Update the existing binding config files to the new format. Bundle is no longer used so Bundle-classes.txt is removed. 2017-05-03 18:36:19 +03:00			`[android.graphics.SurfaceTexture = exceptionMode:nsresult]`
			`[android.view.Surface = exceptionMode:nsresult]`
Bug 1762424 - Generate SDK bindings for android.view.SurfaceControl. r=agi And android.view.SurfaceControl$Transaction. In order to generate these bindings we must increase the maximum SDK version argument we pass to SDKProcessor to 29. However, doing so means that we now attempt to generate bindings for both Surface's Surface(SurfaceTexture) and Surface(SurfaceControl) constructors. These both translate in to C++ functions with identical signatures - Surface::New(jni::Object::Param) - causing a compilation failure. This patch therefore also allows the stubName property to override constructor names, and overrides the latter to Surface::FromSurfaceControl(), thereby avoiding the conflict. Differential Revision: https://phabricator.services.mozilla.com/D143484 2022-04-18 21:11:07 +03:00			`<init>(Landroid/view/SurfaceControl;)V = stubName:FromSurfaceControl, exceptionMode:abort`
			`[android.view.SurfaceControl = exceptionMode:nsresult]`
Bug 1767128 - Rework and re-enable SurfaceControl rendering path on Android. r=agi,gfx-reviewers,aosmond In bug 1762424 we introduced a rendering path on Android using the SurfaceControl API, in order to work around a bug preventing recovery from a GPU process crash. However, the initial implementation caused this bug: repeatedly sending the same SurfaceControl objects over AIDL to the GPU process resulted in them being leaked, eventually causing severe display issues. Not only were we duplicating the SurfaceControl for each widget, but each time a widget was resized too. This patch reworks our usage of the SurfaceControl API to avoid ever having to send them cross-process. Instead, we create a single child SurfaceControl object for each SurfaceControl that is attached to a widget. (Typically there will be a single one shared between all widgets, changing only when the app is paused and resumed, which is much fewer than one per widget per resize.) In the parent process we obtain the Surfaces that will be rendered in to from the child SurfaceControls, and only send those Surfaces to the GPU process. Thankfully unlike SurfaceControls, sending Surfaces cross-process does not cause leaks. When the GPU process dies we simply destroy all of the child SurfaceControls, and recreate them again on-demand. Differential Revision: https://phabricator.services.mozilla.com/D147437 2022-05-31 21:41:07 +03:00			`isValid()Z = exceptionMode:abort`