Some ashmem based objects can not be created due to file descriptor leak

最新推荐文章于 2021-05-25 19:06:39 发布
最新推荐文章于 2021-05-25 19:06:39 发布
阅读量8.8k 收藏 5
点赞数 1
分类专栏： MIB职涯 文章标签： file_descriptor_leak
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/zirconsdu/article/details/8756058
版权

记录了Android系统上基于ashmem或Fd的一些对象由于进程内文件描述符耗尽不能被创建的Issues。

Example One.

06-22 22:38:05.949 27928 31688 E CursorWindow: Could not allocate CursorWindow '/data/data/com.android.providers.downloads/databases/downloads.db' of size 2097152due to error -24.

06-22 22:38:05.969 27928 31688 W dalvikvm: threadid=16: thread exiting with uncaught exception (group=0x40adf9f0)

06-22 22:38:05.989 27928 31688 E AndroidRuntime: FATAL EXCEPTION: Download Service

06-22 22:38:05.989 27928 31688 E AndroidRuntime: android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed.

06-22 22:38:05.989 27928 31688 E AndroidRuntime:  at android.database.CursorWindow.<init>(CursorWindow.java:104)

06-22 22:38:05.989 27928 31688 E AndroidRuntime:  at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)

06-22 22:38:05.989 27928 31688 E AndroidRuntime:  at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:162)

06-22 22:38:05.989 27928 31688 E AndroidRuntime:  at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:156)

06-22 22:38:05.989 27928 31688 E AndroidRuntime:  at android.content.ContentResolver.query(ContentResolver.java:317)

06-22 22:38:05.989 27928 31688 E AndroidRuntime:  at com.android.providers.downloads.DownloadService$UpdateThread.run(DownloadService.java:307)

06-22 22:38:06.059   371  1289 W ActivityManager: Force-killing crashed app android.process.media at watcher's request

06-22 22:38:06.099   371  1288 I ActivityManager: Process android.process.media (pid 27928) has died.

06-22 22:38:06.099   371  1288 W ActivityManager: Scheduling restart of crashed service com.android.providers.downloads/.DownloadService in 5000ms

06-22 22:38:06.099   371  1288 W ActivityManager: Scheduling restart of crashed service com.android.providers.media/.MtpService in 34999ms

Before these lines, there are too many following lines,

06-26 16:28:25.519 I/DownloadManager(13356): Initiating request for download 46

                       **** in DownloadThread::run@DownloadThread.java. called in DownloadInfo::startDownloadThread().

06-26 16:28:25.679 D/-heap   (13356): GC_CONCURRENT freed 1080K, 18% free 7724K/9379K, paused 11ms+49ms

06-26 16:28:25.979 D/ActivityThread(13356): Loading provider downloads: com.android.providers.downloads.DownloadProvider

                      **** in ActivityThread::installProvider@ActivityThread.java, which is called in acquireProvider(arg0, arg1) & installContentProviders

06-26 16:28:26.139 D/ActivityThread(13356): Loading provider downloads: com.android.providers.downloads.DownloadProvider

06-26 16:28:26.329 D/ActivityThread(13356): Loading provider downloads: com.android.providers.downloads.DownloadProvider

06-26 16:28:26.499 D/ActivityThread(13356): Loading provider downloads: com.android.providers.downloads.DownloadProvider

 

Example Two.

Can’t open DB due to too many open files

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin] Error intestSendEmailWithAttachment:

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]android.database.sqlite.SQLiteCantOpenDatabaseException: unable to open database file

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atandroid.database.sqlite.SQLiteDatabase.dbopen(Native Method)

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atandroid.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:1017

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atandroid.database.sqlite.SQLiteDatabase.openDatabase(SQLiteDatabase.java:990)

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atandroid.database.sqlite.SQLiteDatabase.openOrCreateDatabase(SQLiteDatabase.java:1055)

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atandroid.app.ContextImpl.openOrCreateDatabase(ContextImpl.java:803)

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atandroid.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:157)

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atcom.android.email.provider.EmailProvider.getDatabase(EmailProvider.java:879)

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atcom.android.email.provider.EmailProvider.query(EmailProvider.java:1866)

04-23 15:27:32.251 15705 15732 ISystem.out: [stdin]           atandroid.content.ContentProvider$Transport.query(ContentProvider.java:178)

……

…...

04-23 15:27:32.261 15742 15756 ITestRunner: started:testSendEmailWithAttachment(com.android.email.activity.SendEmailWithATTTest)

 

04-13 21:42:12.350  6762  6831 E CursorWindow:Could not allocateCursorWindow '/data/data/com.android.email/databases/EmailProvider.db' of size 2097152 due to error -24.

04-13 21:42:12.360  6762  6831 W System.err: android.database.CursorWindowAllocationException: Cursor window allocation of 2048 kb failed. # Open Cursors=685 (# cursors opened by this proc=685)

04-13 21:42:12.360  6762  6831 W System.err:         at android.database.CursorWindow.<init>(CursorWindow.java:104)

04-13 21:42:12.360  6762  6831 W System.err:         at android.database.AbstractWindowedCursor.clearOrCreateWindow(AbstractWindowedCursor.java:198)

04-13 21:42:12.360  6762  6831 W System.err:         at android.database.sqlite.SQLiteCursor.fillWindow(SQLiteCursor.java:162)

04-13 21:42:12.360  6762  6831 W System.err:         at android.database.sqlite.SQLiteCursor.getCount(SQLiteCursor.java:156)

04-13 21:42:12.370  6762  6831 W System.err:         at android.database.AbstractCursor.moveToPosition(AbstractCursor.java:161)

04-13 21:42:12.370  6762  6831 W System.err:         at com.android.email.provider.ContentCache.putCursor(ContentCache.java:478)

04-13 21:42:12.370  6762  6831 W System.err:         at com.android.email.provider.EmailProvider.query(EmailProvider.java:1970)

04-13 21:42:12.370  6762  6831 W System.err:         at com.android.email.provider.EmailProvider.preCacheTable(EmailProvider.java:927)

04-13 21:42:12.370  6762  6831 W System.err:         at com.android.email.provider.EmailProvider.preCacheData(EmailProvider.java:988)

04-13 21:42:12.370  6762  6831 W System.err:         at com.android.email.provider.EmailProvider.getDatabase(EmailProvider.java:909)

04-13 21:42:12.380  6762  6831 W System.err:         at com.android.email.provider.EmailProvider.query(EmailProvider.java:1866)

04-13 21:42:12.380  6762  6831 W System.err:         at android.content.ContentProvider$Transport.query(ContentProvider.java:178)

04-13 21:42:12.380  6762  6831 W System.err:         at android.content.ContentResolver.query(ContentResolver.java:311)

•when the issue happens, there always are the multiple loading of email provider observed from log file.
•04-13 21:41:56.670  6762  6831 D ActivityThread: Loading provider com.android.email.provider;com.android.email.notifier: com.android.email.provider.EmailProvider
•04-13 21:41:57.060  6762  6776 D ActivityThread:Loading provider com.android.email.provider;com.android.email.notifier: com.android.email.provider.EmailProvider
•04-13 21:41:57.400  6762  6776 D ActivityThread: Loading provider com.android.email.provider;com.android.email.notifier: com.android.email.provider.EmailProvider
•04-13 21:41:57.590  6762  6776 D ActivityThread: Loading provider com.android.email.provider;com.android.email.notifier: com.android.email.provider.EmailProvider
 
Example three.

02-03 20:04:52.427 E/InputChannel-JNI(  886): Error 24 dup channel fd 1009.
02-03 20:04:52.447 I/DropBoxManager(  604): tag = system_app_crash; data = Process: com.android.phone
02-03 20:04:52.447 I/DropBoxManager(  604):
02-03 20:04:52.447 I/DropBoxManager(  604): java.lang.RuntimeException: Could not read input channel file descriptors from parcel.
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.InputChannel.nativeReadFromParcel(Native Method)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.InputChannel.readFromParcel(InputChannel.java:135)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.IWindowSession$Stub$Proxy.add(IWindowSession.java:523)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.ViewRootImpl.setView(ViewRootImpl.java:551)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:326)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.WindowManagerImpl.addView(WindowManagerImpl.java:224)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.WindowManagerImpl$CompatModeWrapper.addView(WindowManagerImpl.java:149)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.view.Window$LocalWindowManager.addView(Window.java:547)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2650)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2095)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.app.ActivityThread.access$600(ActivityThread.java:136)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1201)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.os.Handler.dispatchMessage(Handler.java:99)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.os.Looper.loop(Looper.java:137)
02-03 20:04:52.447 I/DropBoxManager(  604):  at android.app.ActivityThread.main(ActivityThread.java:4790)
02-03 20:04:52.447 I/DropBoxManager(  604):  at java.lang.reflect.Method.invokeNative(Native Method)
02-03 20:04:52.447 I/DropBoxManager(  604):  at java.lang.reflect.Method.invoke(Method.java:511)
02-03 20:04:52.447 I/DropBoxManager(  604):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:798)
02-03 20:04:52.447 I/DropBoxManager(  604):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:565)
02-03 20:04:52.447 I/DropBoxManager(  604):  at dalvik.system.NativeStart.main(Native Method)

02-03 20:04:52.367 E/CursorWindow(  886):Could not create CursorWindow from Parcel due to error -24.
02-03 20:04:52.447 W/AsyncQuery(  886): Exception thrown during handling EVENT_ARG_QUERY
02-03 20:04:52.447 W/AsyncQuery(  886): android.database.CursorWindowAllocationException: Cursor window could not be created from binder.
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.database.CursorWindow.<init>(CursorWindow.java:133)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.database.CursorWindow.<init>(CursorWindow.java:41)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.database.CursorWindow$1.createFromParcel(CursorWindow.java:681)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.database.CursorWindow$1.createFromParcel(CursorWindow.java:679)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.database.BulkCursorDescriptor.readFromParcel(BulkCursorDescriptor.java:75)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.database.BulkCursorDescriptor$1.createFromParcel(BulkCursorDescriptor.java:34)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.database.BulkCursorDescriptor$1.createFromParcel(BulkCursorDescriptor.java:30)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.content.ContentProviderProxy.query(ContentProviderNative.java:369)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.content.ContentResolver.query(ContentResolver.java:370)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.content.ContentResolver.query(ContentResolver.java:313)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.content.AsyncQueryHandler$WorkerHandler.handleMessage(AsyncQueryHandler.java:79)
02-03 20:04:52.447 W/AsyncQuery(  886):  at com.android.internal.telephony.CallerInfoAsyncQuery$CallerInfoAsyncQueryHandler$CallerInfoWorkerHandler.handleMessage(CallerInfoAsyncQuery.java:152)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.os.Handler.dispatchMessage(Handler.java:99)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.os.Looper.loop(Looper.java:137)
02-03 20:04:52.447 W/AsyncQuery(  886):  at android.os.HandlerThread.run(HandlerThread.java:60)

Reason for Example One and Two
are both for DatabaseConnection File descriptor leaks.
 
Analysis for Example Three

From the log
02-03 20:04:52.427 E/InputChannel-JNI(  886): Error 24 dup channel fd 1009.
02-03 20:04:52.447 I/DropBoxManager(  604): java.lang.RuntimeException: Could not read input channel file descriptors from parcel.
and
02-03 20:04:52.367 E/CursorWindow(  886): Could not create CursorWindow from Parcel due to error -24.
02-03 20:04:52.447 W/AsyncQuery(  886): Exception thrown during handling EVENT_ARG_QUERY

File descriptors are used out when the app dups InputChannel and CursorWindow FDs.
The app dups FDs transferred from the binder to use the ashmem for InputChannel or CursorWindow.

The FD in "Error 24 dup channel fd 1009" is 1009, a little less than max number of Fds a process can open.
When FDs are used out, error occurs in FDs dup.

So, there is InputChannel or Cursor or common FD leaks in the phone app.

It was found at last that there are binder fd leaks in the phone app. 
    public void release() @ XxxxCallerInfoHandler.java
    {
        mIsReady = false;
        if (mCallTimer != null)
            mCallTimer.cancelTimer();
        mCallTimer = null;

        mCallInfoHandler = null;

        // Fixed the binder leak issue.
        if (mLoadSnsThreadHandler != null)
        {
            mLoadSnsThreadHandler.removeMessages(EVENT_LOAD_SNS);
            mLoadSnsThreadHandler.getLooper().quit();
            mLoadSnsThreadHandler = null;
        }
    }
所以，遇到errno -24，EMFILE，这样的问题，就是竭尽所能找到耗尽File Descriptors的代码所在。
出错的地方并不一定是原因所在，如果有Ramdump这是比较容易的事情。
 
END
zirconsdu
关注
专栏目录
Android SQLite数据库异常: unable to open database file
ZhangJian的博客
11-23 6813
SQLite异常问题
Android MemoryFile内存文件 + Ashmem匿名共享内存，flutter瀑布流布局加载更多
m0_66145114的博客
03-06 367
} finally { endAccess(); } } JNI：./frameworks/base/core/jni/android_os_MemoryFile.cpp namespace android { static jboolean android_os_MemoryFile_pin(JNIEnv* env, jobject clazz, jobject fileDescriptor, jboolean pin) { int fd = jniGetFDFromFileDescriptor(env,
File Descriptor Leak
weixin_30740295的博客
02-13 505
https://martin-ueding.de/articles/c-file-descriptors/index.html http://blog.sina.com.cn/s/blog_605f5b4f01013lgv.html (good) https://docs.oracle.com/cd/E23095_01/Platform.93/ATGInstallGuide/html/s06...
Could not read input channel file descriptors from parce问题分析解决
为码消得人憔悴
06-05 7801
最近项目Monkey测试的时候A应用总是出现如下问题，导致Crash06-30 11:43:36.160 23438 23438 E InputChannel-JNI: Error 24 dup channel fd 74. 06-30 11:43:36.161 23438 23438 D AndroidRuntime: Shutting down VM 06-30 11:43:36.161 23...
Could not read input channel file descriptors from parcel
yanggz888的专栏
04-02 4223
[Exception] Could not read input channel file descriptors from parcel. 1.RemoteView中添加的图片太大了，超过40K会报这个异常 2.Intent传递的数据太大了超过1M也会报这个错误 3.FileDescripter太多而且没有关闭，looper太多没有quit。 4.试试在AndroidMane
android FD leak 定位文件泄漏
lei7143的专栏
09-27 2370
R 上google 加入了一个fd leak 检测功能，基本实现如下： SystemServer.java 中在system_server 进程创建一个Native 检测进程 spawnFdLeakCheckThread(); frameworks/base/services/core/jni/com_android_server_SystemServer.cpp
android进程间socket传递Ashmem的文件描述符
05-12
但是，Ashmem分配的内存可以像文件一样通过文件描述符（File Descriptor）进行操作。这样，一个进程创建的Ashmem内存区域，可以通过IPC的方式将文件描述符传递给其他进程，从而实现跨进程的数据共享。 在Android中...
安卓Ashmem使用实列
11-18
安卓很多模块都用到了ashmem，为了更好的学习各个模块，了解ashmem的原理是必不可少的！
且听穿林打叶声———Ashmem机制讲解
十年代码写十年
05-07 414
在Android平台上，提供了一种共享内存的机制——Ashmem。该机制内部其实复用了Linux的共享内存机制。Ashmem机制使用linux的mmap系统调用，可以将同一段物理内存映射到不同进程各自的虚拟地址空间，从而实现高效的进程间共享。 大家都知道，在linux上“一切皆文件”，一块共享内存当然也不例外。因此，在用户态，我们能看到的重要概念就是共享内存的“文件描述符”，文件描述符可以对应一...
【安卓笔记】AsyncQueryHandler源码剖析
RowandJJ
09-05 2548
AsyncQueryHandler类用于提供异步数据库操作（增删改查）功能。本文视图从源码角度分析这个类。 1.AsyncQueryHandler使用方式： AsyncQueryHandler handler = new AsyncQueryHandler(this.getContentResolver()) { @Override protected void
android 多界面光标,android.database.CursorWindowAllocationException：光标窗口分配2048 kb失败,即使关闭游标...
weixin_32629853的博客
05-25 799
关于CursorWindowAllocatoinException有很多关于SO的问题：他们都建议游标在使用后必须关闭.但这并没有解决我的问题.这是我的代码：String query = "select serial from tbl1 union select serial from tbl2 union select serial from tbl3";sqliteDatabase db = ...
java mms处理_MMS源码中异步处理简析
weixin_33824590的博客
02-13 279
1，信息数据的查询，删除使用AsycnQueryHandler处理AsycnQueryHandler继承了Handlerpublic abstract class AsyncQueryHandler extends Handler内部使用HandleThread来实现异步线程处理数据，成员变量也有一个Handler并拥有HandleThread的looper。privateHandler mWor...
[已解决]Could not allocate CursorWindow '' of size of size 2097152 due to error -12.
Kodulf的专栏
07-28 1万+
Could not allocate CursorWindow '/data/data/com.wbm.app.activity/databases/cashierDB.db' of size 2097152 due to error -12. 07-26 16:28:14.067 9407-9654/? W/System.err: android.database.CursorWind
Android 内存管理 &Memory Leak & OOM 分析
热门推荐
vshuang的专栏
09-28 3万+
1、Android 进程管理&amp;内存 Android主要应用在嵌入式设备当中，而嵌入式设备由于一些众所周知的条件限制，通常都不会有很高的配置，特别是内存是比较有限的。如果我们编写的代 码当中有太多的对内存使用不当的地方，难免会使得我们的设备运行缓慢，甚至是死机。为了能够使得Android应用程序安全且快速的运行，Android 的每个应用程序都会使用一个专有的Dalvik虚拟机实例来运行，...
解决句柄泄露（fd leak）[error: Too many open files]
苏格兰狗饼的博客
03-06 1248
接手老项目（历史遗留下来的bug） 这个项目跑的是rk3288板子， adb检验appid是否为句柄泄露 adb devices List of devices attached P1QRMFV6HD device 192.168.100.188:5555 device adb -s P1QRMFV6HD shell shell@YoungFeel:/ $ su root@Youn...
Android句柄泄漏（Fd leak）排查
weixin_34097242的博客
04-26 3774
背景 句柄泄漏（Fd leak）不是什么新鲜问题了，网上一搜这种问题，有很多种解决办法。 但没有系统性，导致排查问题效率极低。笔者希望通过这一篇文章，帮助大家理清思路，快速解决问题。 排查问题的黄金步骤 查log 找复现步骤 查代码 本文也将按照这几步，逐步深入到问题中。 查log 一般发生这种问题时，堆栈如下： java.lang.RuntimeException Could not rea...
Jenkins中无法启动子进程的解决办法
wangbin0016的专栏
12-15 7253
Jenkins中无法启动子进程的解决办法  先介绍下场景： 在Jenkins中新建了一个Job，假设你在一些列Build Step之前/之后，启动了一个进程，打个比方说启动一个Jboss进程。等到Build完成，你去Console Output中查看显示启动成功，甚至PID也有了。但是当你去后台查看的时候，发现其实这个进程根本不存在，并没有启动成功。 不过
跑monkey过程中，出现systemserver重启现象
一杯咖啡的专栏
09-07 2810
08-27 18:36:58.131318 900 921 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: ActivityManager 08-27 18:36:58.131318 900 921 E AndroidRuntime: java.lang.IllegalArgumentException: No d...
Android Pmem与Ashmem详解：共享内存机制与差异
"本文主要介绍了Android中的Pmem和Ashmem技术，其中重点讲解了Ashmem的工作原理和特性，包括其如何利用mmap实现共享内存，以及与cache shrinker的关联来实现智能内存回收。" 在Android系统中，Pmem（Persistent ...
评论 3
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值