Android
!!! FAILED BINDER TRANSACTION !!!
墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年，写一次发全网
我也要 关注 + 加入社区如题，在Android中偶现service crash的问题，
log如下：
SceneFile: Unhandled atrribute: flippable=false for circle_expand/circlefront
09-16 12:27:56.738 422 422 W SceneFile: Scenefile references a node that no longer exists: circle_weather/windowfront
09-16 12:27:56.742 422 422 W SceneFile: Unhandled atrribute: flippable=false for circle_help/circlefront
09-16 12:27:56.742 422 422 W SceneFile: Scenefile references a node that no longer exists: circle_weather/windowback
09-16 12:27:56.757 247 255 E JavaBinder: !!! FAILED BINDER TRANSACTION !!!
09-16 12:27:56.757 247 255 W ActivityManager: Scheduling restart of crashed service com.motorola.widget.circlewidget3d/.CircleWidget3DProvider$CircleService in 5000ms
09-16 12:27:56.761 247 549 I WindowState: WIN DEATH: Window{42d8f2f8 SurfaceView paused=false}
09-16 12:27:56.761 247 247 I WindowState: WIN DEATH: Window{42d04fb8 com.motorola.blur.weather/com.motorola.blur.weather2.WeatherActivity2 paused=false}
09-16 12:27:56.781 247 255 W ActivityManager: Exception when starting service com.motorola.widget.circlewidget3d/.CircleWidget3DProvider$CircleService
09-16 12:27:56.781 247 255 W ActivityManager: android.os.TransactionTooLargeException
09-16 12:27:56.781 247 255 W ActivityManager: at android.os.BinderProxy.transact(Native Method)
09-16 12:27:56.781 247 255 W ActivityManager: at android.app.ApplicationThreadProxy.scheduleCreateService(ApplicationThreadNative.java:802)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.realStartServiceLocked(ActivityManagerService.java:11352)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.bringUpServiceLocked(ActivityManagerService.java:11539)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.bindService(ActivityManagerService.java:12110)
09-16 12:27:56.781 247 255 W ActivityManager: at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:728)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1611)
09-16 12:27:56.781 247 255 W ActivityManager: at android.os.Binder.execTransact(Binder.java:367)
09-16 12:27:56.781 247 255 W ActivityManager: at dalvik.system.NativeStart.run(Native Method)
09-16 12:27:56.781 247 2375 I ActivityManager: Process com.motorola.widget.circlewidget3d (pid 3873) has died.
帮忙看下是什么原因啊？
log如下：
SceneFile: Unhandled atrribute: flippable=false for circle_expand/circlefront
09-16 12:27:56.738 422 422 W SceneFile: Scenefile references a node that no longer exists: circle_weather/windowfront
09-16 12:27:56.742 422 422 W SceneFile: Unhandled atrribute: flippable=false for circle_help/circlefront
09-16 12:27:56.742 422 422 W SceneFile: Scenefile references a node that no longer exists: circle_weather/windowback
09-16 12:27:56.757 247 255 E JavaBinder: !!! FAILED BINDER TRANSACTION !!!
09-16 12:27:56.757 247 255 W ActivityManager: Scheduling restart of crashed service com.motorola.widget.circlewidget3d/.CircleWidget3DProvider$CircleService in 5000ms
09-16 12:27:56.761 247 549 I WindowState: WIN DEATH: Window{42d8f2f8 SurfaceView paused=false}
09-16 12:27:56.761 247 247 I WindowState: WIN DEATH: Window{42d04fb8 com.motorola.blur.weather/com.motorola.blur.weather2.WeatherActivity2 paused=false}
09-16 12:27:56.781 247 255 W ActivityManager: Exception when starting service com.motorola.widget.circlewidget3d/.CircleWidget3DProvider$CircleService
09-16 12:27:56.781 247 255 W ActivityManager: android.os.TransactionTooLargeException
09-16 12:27:56.781 247 255 W ActivityManager: at android.os.BinderProxy.transact(Native Method)
09-16 12:27:56.781 247 255 W ActivityManager: at android.app.ApplicationThreadProxy.scheduleCreateService(ApplicationThreadNative.java:802)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.realStartServiceLocked(ActivityManagerService.java:11352)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.bringUpServiceLocked(ActivityManagerService.java:11539)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.bindService(ActivityManagerService.java:12110)
09-16 12:27:56.781 247 255 W ActivityManager: at android.app.ActivityManagerNative.onTransact(ActivityManagerNative.java:728)
09-16 12:27:56.781 247 255 W ActivityManager: at com.android.server.am.ActivityManagerService.onTransact(ActivityManagerService.java:1611)
09-16 12:27:56.781 247 255 W ActivityManager: at android.os.Binder.execTransact(Binder.java:367)
09-16 12:27:56.781 247 255 W ActivityManager: at dalvik.system.NativeStart.run(Native Method)
09-16 12:27:56.781 247 2375 I ActivityManager: Process com.motorola.widget.circlewidget3d (pid 3873) has died.
帮忙看下是什么原因啊？
...全文
相关推荐
BinderJava
Binder简化例子， 只使用java演示Binder和Service实现。希望对写新的跨进程Service有帮助。
Android的IPC机制Binder的各个部分.pdf
Android的IPC机制Binder的各个部分.pdf
Android Binder 机制学习总结
Android Binder 机制学习总结 Android Binder 机制学习总结
CVE-2020-0041:适用于Android Binder错误CVE-2020-0041的漏洞
CVE-2020-0041 该存储库包含用于利用CVE-2020-0041的代码，这是我们于2019年12月向Google报告的错误，并已于2020年3月在Android安全公告中修复。 您可以在找到沙箱逃生漏洞。 可以在找到对该错误和利用方法的分析。 同样，您可以在找到特权升级漏洞。 可在找到此部分的开发方法。
AndroidBinder
Binder是什么？Binder是一种进程间通信机制为什么是Binder？Binder通信机制采用C/S架构，这很重要！！！@Binder架构|centerBinder框架中主要涉及到4个角色Client、Server、ServiceManager及Binder驱动，其中Client、Server、ServiceManager运行在用户空间，Binder驱动运行在内核空间Client代表客户端进程，Server代表客户端进程提供各种服务，如音视频等ServiceManager用来管理各种系统服务Binder驱动提供进程间通信的能力用户空间的Client、Server、ServiceManage
