Could not create epoll instance: Too many open files 问题引起的内存泄露

最新推荐文章于 2022-11-08 17:11:00 发布
最新推荐文章于 2022-11-08 17:11:00 发布
阅读量2.4k 收藏
点赞数 1
分类专栏： Android mina could not create epoll instanc too many open files
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/OoOzZL/article/details/82497005
版权

问题：开发的app，在测试环境运行没有问题，但是在预发布环境，每隔3至4分钟就会崩溃，灰常有规律…溃日志如下：

--------- beginning of crash
09-07 10:56:27.755 12156 12156 E AndroidRuntime: FATAL EXCEPTION: main
09-07 10:56:27.755 12156 12156 E AndroidRuntime: Process: com.example.package, PID: 12156
09-07 10:56:27.755 12156 12156 E AndroidRuntime: java.lang.RuntimeException: Could not read input channel file descriptors from parcel.
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.view.InputChannel.nativeReadFromParcel(Native Method)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.view.InputChannel.readFromParcel(InputChannel.java:148)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.view.InputChannel$1.createFromParcel(InputChannel.java:39)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.view.InputChannel$1.createFromParcel(InputChannel.java:37)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at com.android.internal.view.InputBindResult.<init>(InputBindResult.java:68)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at com.android.internal.view.InputBindResult$1.createFromParcel(InputBindResult.java:112)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at com.android.internal.view.InputBindResult$1.createFromParcel(InputBindResult.java:110)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at com.android.internal.view.IInputMethodManager$Stub$Proxy.startInputOrWindowGainedFocus(IInputMethodManager.java:723)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.view.inputmethod.InputMethodManager.startInputInner(InputMethodManager.java:1301)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.view.inputmethod.InputMethodManager.onPostWindowFocus(InputMethodManager.java:1549)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.view.ViewRootImpl$ViewRootHandler.handleMessage(ViewRootImpl.java:3923)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:106)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:164)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at android.app.ActivityThread.main(ActivityThread.java:6600)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:518)
09-07 10:56:27.755 12156 12156 E AndroidRuntime:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:821)
09-07 10:56:27.759 12156 12611 F Looper  : Could not create epoll instance: Too many open files
09-07 10:56:27.760 12156 12156 W System.err: java.lang.RuntimeException: Could not read input channel file descriptors from parcel.
09-0    7 10:56:27.761 12156 12156 W System.err:    at android.view.InputChannel.nativeReadFromParcel(Native Method)
09-07 10:56:27.761 12156 12156 W System.err:    at android.view.InputChannel.readFromParcel(InputChannel.java:148)
09-07 10:56:27.761 12156 12156 W System.err:    at android.view.InputChannel$1.createFromParcel(InputChannel.java:39)
09-07 10:56:27.761 12156 12156 W System.err:    at android.view.InputChannel$1.createFromParcel(InputChannel.java:37)
09-07 10:56:27.761 12156 12156 W System.err:    at com.android.internal.view.InputBindResult.<init>(InputBindResult.java:68)
09-07 10:56:27.761 12156 12156 W System.err:    at com.android.internal.view.InputBindResult$1.createFromParcel(InputBindResult.java:112)
09-07 10:56:27.761 12156 12156 W System.err:    at com.android.internal.view.InputBindResult$1.createFromParcel(InputBindResult.java:110)
09-07 10:56:27.761 12156 12156 W System.err:    at com.android.internal.view.IInputMethodManager$Stub$Proxy.startInputOrWindowGainedFocus(IInputMethodManager.java:723)
09-07 10:56:27.761 12156 12156 W System.err:    at android.view.inputmethod.InputMethodManager.startInputInner(InputMethodManager.java:1301)
09-07 10:56:27.761 12156 12156 W System.err:    at android.view.inputmethod.InputMethodManager.onPostWindowFocus(InputMethodManager.java:1549)
09-07 10:56:27.761 12156 12156 W System.err:    at android.view.ViewRootImpl$ViewRootHandler.handleMessage(ViewRootImpl.java:3923)
09-07 10:56:27.761 12156 12156 W System.err:    at android.os.Handler.dispatchMessage(Handler.java:106)
09-07 10:56:27.762 12156 12156 W System.err:    at android.os.Looper.loop(Looper.java:164)
09-07 10:56:27.762 12156 12156 W System.err:    at android.app.ActivityThread.main(ActivityThread.java:6600)
09-07 10:56:27.762 12156 12156 W System.err:    at java.lang.reflect.Method.invoke(Native Method)
09-07 10:56:27.762 12156 12156 W System.err:    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:518)
09-07 10:56:27.762 12156 12156 W System.err:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:821)
09-07 10:56:27.815 12156 12156 W System.err: java.io.IOException: Cannot run program "cat": error=24, Too many open files
09-07 10:56:27.815 12156 12156 W System.err:    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
09-07 10:56:27.815 12156 12156 W System.err:    at java.lang.Runtime.exec(Runtime.java:692)zhangxs123&@
09-07 10:56:27.816 12156 12156 W System.err:    at java.lang.Runtime.exec(Runtime.java:560)
09-07 10:56:27.816 12156 12156 W System.err:    at com.example.package.safe.CrashHandler.collectMemInfo(CrashHandler.java:286)
09-07 10:56:27.816 12156 12156 W System.err:    at com.example.package.safe.CrashHandler.collectInfo(CrashHandler.java:160)
09-07 10:56:27.816 12156 12156 W System.err:    at com.example.package.safe.CrashHandler.catchCrashException(CrashHandler.java:125)
09-07 10:56:27.816 12156 12156 W System.err:    at com.example.package.safe.CrashHandler.uncaughtException(CrashHandler.java:97)
09-07 10:56:27.816 12156 12156 W System.err:    at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1068)
09-07 10:56:27.816 12156 12156 W System.err:    at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1063)
09-07 10:56:27.816 12156 12156 W System.err:    at java.lang.Thread.dispatchUncaughtException(Thread.java:1955)
09-07 10:56:27.816 12156 12156 W System.err: Caused by: java.io.IOException: error=24, Too many open files
09-07 10:56:27.816 12156 12156 W System.err:    at java.lang.UNIXProcess.forkAndExec(Native Method)
09-07 10:56:27.816 12156 12156 W System.err:    at java.lang.UNIXProcess.<init>(UNIXProcess.java:133)
09-07 10:56:27.817 12156 12156 W System.err:    at java.lang.ProcessImpl.start(ProcessImpl.java:128)
09-07 10:56:27.817 12156 12156 W System.err:    at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
09-07 10:56:27.817 12156 12156 W System.err:    ... 9 more
09-07 10:56:27.824 12156 12156 W System.err: java.io.FileNotFoundException: /storage/emulated/0/hbsqjz/crash/crash-2018-09-07-10-56-27.log (Too many open files)
09-07 10:56:27.824 12156 12156 W System.err:    at java.io.FileOutputStream.open0(Native Method)
09-07 10:56:27.824 12156 12156 W System.err:    at java.io.FileOutputStream.open(FileOutputStream.java:287)
09-07 10:56:27.824 12156 12156 W System.err:    at java.io.FileOutputStream.<init>(FileOutputStream.java:223)
09-07 10:56:27.824 12156 12156 W System.err:    at java.io.FileOutputStream.<init>(FileOutputStream.java:110)
09-07 10:56:27.824 12156 12156 W System.err:    at com.example.package.safe.CrashHandler.saveCrashInfo2File(CrashHandler.java:323)
09-07 10:56:27.824 12156 12156 W System.err:    at com.example.package.safe.CrashHandler.catchCrashException(CrashHandler.java:127)
09-07 10:56:27.824 12156 12156 W System.err:    at com.example.package.safe.CrashHandler.uncaughtException(CrashHandler.java:97)
09-07 10:56:27.825 12156 12156 W System.err:    at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1068)
09-07 10:56:27.825 12156 12156 W System.err:    at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:1063)
09-07 10:56:27.825 12156 12156 W System.err:    at java.lang.Thread.dispatchUncaughtException(Thread.java:1955)
09-07 10:56:27.962 12615 12615 I crash_dump64: obtaining output fd from tombstoned, type: kDebuggerdTombstone
09-07 10:56:27.963  1149  1149 I /system/bin/tombstoned: received crash request for pid 12156
09-07 10:56:27.964 12615 12615 I crash_dump64: performing dump of process 12156 (target tid = 12611)
09-07 10:56:27.964 12615 12615 F DEBUG   : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-07 10:56:27.964 12615 12615 F DEBUG   : Build fingerprint: 'xiaomi/whyred/whyred:8.1.0/OPM1.171019.011/V9.5.12.0.OEICNFA:user/release-keys'
09-07 10:56:27.964 12615 12615 F DEBUG   : Revision: '0'
09-07 10:56:27.964 12615 12615 F DEBUG   : ABI: 'arm64'
09-07 10:56:27.964 12615 12615 F DEBUG   : pid: 12156, tid: 12611, name: Thread-70  >>> com.example.package <<<
09-07 10:56:27.964 12615 12615 F DEBUG   : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
09-07 10:56:27.968 12615 12615 F DEBUG   : Abort message: 'jniInit'
09-07 10:56:27.968 12615 12615 F DEBUG   :     x0   0000000000000000  x1   0000000000003143  x2   0000000000000006  x3   0000000000000008
09-07 10:56:27.968 12615 12615 F DEBUG   :     x4   0000000000000000  x5   0000000000000000  x6   0000000000000000  x7   7f7f7f7f7f7f7f7f
09-07 10:56:27.968 12615 12615 F DEBUG   :     x8   0000000000000083  x9   7e97b88a5f20cc4e  x10  0000000000000000  x11  0000000000000001
09-07 10:56:27.968 12615 12615 F DEBUG   :     x12  ffffffffffffffff  x13  ffffffffffffffff  x14  ff00000000000000  x15  ffffffffffffffff
09-07 10:56:27.968 12615 12615 F DEBUG   :     x16  00000002aed13fa8  x17  00000072b32f964c  x18  0000007230284470  x19  0000000000002f7c
09-07 10:56:27.968 12615 12615 F DEBUG   :     x20  0000000000003143  x21  00000072223e5000  x22  0000007217135588  x23  0000007217135588
09-07 10:56:27.968 12615 12615 F DEBUG   :     x24  0000000000000000  x25  0000007217135588  x26  00000072223e50a0  x27  0000000000000000
09-07 10:56:27.968 12615 12615 F DEBUG   :     x28  0000000000000000  x29  0000007217133850  x30  00000072b32aeeac
09-07 10:56:27.968 12615 12615 F DEBUG   :     sp   0000007217133810  pc   00000072b32aeec8  pstate 0000000060000000
09-07 10:56:28.246 12615 12615 F DEBUG   : 
09-07 10:56:28.246 12615 12615 F DEBUG   : backtrace:
09-07 10:56:28.246 12615 12615 F DEBUG   :     #00 pc 000000000001dec8  /system/lib64/libc.so (abort+104)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #01 pc 0000000000007f20  /system/lib64/liblog.so (__android_log_assert+304)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #02 pc 00000000000156a8  /system/lib64/libutils.so (android::Looper::rebuildEpollLocked()+348)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #03 pc 0000000000015508  /system/lib64/libutils.so (android::Looper::Looper(bool)+236)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #04 pc 000000000011090c  /system/lib64/libandroid_runtime.so (android::NativeMessageQueue::NativeMessageQueue()+160)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #05 pc 000000000011123c  /system/lib64/libandroid_runtime.so (android::android_os_MessageQueue_nativeInit(_JNIEnv*, _jclass*)+28)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #06 pc 0000000000622420  /system/framework/arm64/boot-framework.oat (offset 0x622000) (android.os.Binder.clearCallingIdentity [DEDUPED]+144)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #07 pc 000000000054824c  /system/lib64/libart.so (art_quick_invoke_static_stub+604)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #08 pc 00000000000dcfb4  /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+260)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #09 pc 000000000029a474  /system/lib64/libart.so (art::interpreter::ArtInterpreterToCompiledCodeBridge(art::Thread*, art::ArtMethod*, art::ShadowFrame*, unsigned short, art::JValue*)+344)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #10 pc 0000000000294a64  /system/lib64/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+696)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #11 pc 00000000005315c0  /system/lib64/libart.so (MterpInvokeStatic+224)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #12 pc 0000000000539f14  /system/lib64/libart.so (ExecuteMterpImpl+14612)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #13 pc 0000000000274ec8  /system/lib64/libart.so (art::interpreter::Execute(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame&, art::JValue, bool)+444)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #14 pc 000000000027aad0  /system/lib64/libart.so (art::interpreter::ArtInterpreterToInterpreterBridge(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame*, art::JValue*)+216)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #15 pc 0000000000294a44  /system/lib64/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+664)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #16 pc 0000000000531404  /system/lib64/libart.so (MterpInvokeDirect+304)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #17 pc 0000000000539e94  /system/lib64/libart.so (ExecuteMterpImpl+14484)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #18 pc 0000000000274ec8  /system/lib64/libart.so (art::interpreter::Execute(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame&, art::JValue, bool)+444)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #19 pc 000000000027aad0  /system/lib64/libart.so (art::interpreter::ArtInterpreterToInterpreterBridge(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame*, art::JValue*)+216)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #20 pc 0000000000294a44  /system/lib64/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+664)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #21 pc 0000000000531404  /system/lib64/libart.so (MterpInvokeDirect+304)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #22 pc 0000000000539e94  /system/lib64/libart.so (ExecuteMterpImpl+14484)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #23 pc 0000000000274ec8  /system/lib64/libart.so (art::interpreter::Execute(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame&, art::JValue, bool)+444)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #24 pc 000000000027aad0  /system/lib64/libart.so (art::interpreter::ArtInterpreterToInterpreterBridge(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame*, art::JValue*)+216)
    09-07 10:56:28.246 12615 12615 F DEBUG   :     #25 pc 0000000000294a44  /system/lib64/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+664)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #26 pc 00000000005315c0  /system/lib64/libart.so (MterpInvokeStatic+224)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #27 pc 0000000000539f14  /system/lib64/libart.so (ExecuteMterpImpl+14612)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #28 pc 0000000000274ec8  /system/lib64/libart.so (art::interpreter::Execute(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame&, art::JValue, bool)+444)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #29 pc 000000000027aad0  /system/lib64/libart.so (art::interpreter::ArtInterpreterToInterpreterBridge(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame*, art::JValue*)+216)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #30 pc 0000000000294a44  /system/lib64/libart.so (_ZN3art11interpreter6DoCallILb0ELb0EEEbPNS_9ArtMethodEPNS_6ThreadERNS_11ShadowFrameEPKNS_11InstructionEtPNS_6JValueE+664)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #31 pc 00000000005315c0  /system/lib64/libart.so (MterpInvokeStatic+224)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #32 pc 0000000000539f14  /system/lib64/libart.so (ExecuteMterpImpl+14612)
    09-07 10:56:28.246 12615 12615 F DEBUG   :     #33 pc 0000000000274ec8  /system/lib64/libart.so (art::interpreter::Execute(art::Thread*, art::DexFile::CodeItem const*, art::ShadowFrame&, art::JValue, bool)+444)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #34 pc 0000000000522e1c  /system/lib64/libart.so (artQuickToInterpreterBridge+1052)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #35 pc 000000000055110c  /system/lib64/libart.so (art_quick_to_interpreter_bridge+92)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #36 pc 0000000000547f88  /system/lib64/libart.so (art_quick_invoke_stub+584)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #37 pc 00000000000dcf78  /system/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+200)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #38 pc 000000000046c5e8  /system/lib64/libart.so (art::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&, art::ArtMethod*, art::ArgArray*, art::JValue*, char const*)+100)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #39 pc 000000000046d814  /system/lib64/libart.so (art::InvokeVirtualOrInterfaceWithJValues(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, jvalue*)+836)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #40 pc 00000000004940f8  /system/lib64/libart.so (art::Thread::CreateCallback(void*)+1120)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #41 pc 0000000000067ec4  /system/lib64/libc.so (__pthread_start(void*)+36)
09-07 10:56:28.246 12615 12615 F DEBUG   :     #42 pc 000000000001f2f4  /system/lib64/libc.so (__start_thread+68)
09-07 10:56:29.167  1149  1149 E /system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_05

日志很长，然而看完后，并没有什么乱用。也有去学习内存分析的知识，但是在这里用不上。
通过android profiler查看，发现内存一直有未小幅度增长，增长区域是native,然而自己并没有编写native相关代码，所以这里的问题没办法查看。
继续看logcat日志，确定mina一直抛出连接失败警告，脑洞大开..以此为切入点，关闭mina，再重新启动app，崩溃的现象就没有了。
网上查找mina断链引发的崩溃问题。。。不甚明白。
关闭mina不是解决方案啊…找服务端人员解决了下链接失败的问题，没有mina断链问题候，崩溃现象也就小时了。。。。
最后还是存在疑惑，mina链接失败的位置，有添加try…catch，但还是会导致这种内存溢出崩溃，很费劲，有没有大神站出来解决一下。。。求关注，求科普

John_ZhangXS
关注
专栏目录
Too many open files
thinker
03-30 991
coredump堆栈 #10 0x00007f1fa8a97ce9 in __run_exit_handlers () from /lib64/libc.so.6 #11 0x00007f1fa8a97d37 in exit () from /lib64/libc.so.6 #12 0x00007f1fa998ba38 in event_exit (errcode=errcode@entry=1) at log.c:103 #13 0x00007f1fa998bde7 in event_sock_err
记一次tomcat报错Too many open files的排查历程
zxx的专栏
01-09 7054
本文的技术细节并不具通用性，但是排查的思路过程值得自己mark下，上次遇到这样的刺激线上故障已经是去年3月了～～～这次排查花了3个小时，还算快啦，也算最近的一个小彩蛋。 昨天在公司coding，测试组的同事突然来找我，告知预发环境的系统挂了，请求都是异常，打开业务日志和tomcat的日志排查，满屏的Too many open files，果然 lsof -p pid 预发机器，已经打满到了655...
Linux "Too many open files" 问题分析
zangdongming的专栏
07-12 2188
平台介绍：Linux3.10.40 + Android4.4.2   事情的起因是压力测试过程中生成的tombstone日志异常，日志形式如下： ======================================================================= *** *** *** *** *** *** *** *** *** *** *** *** ***
从 A/Looper: Could not create epoll instance. errno=24 错误浅谈解决各种 bug 的思路
weixin_33738982的博客
06-03 266
今天代码写着写着就莫名闪退了，手机也没有“程序停止运行”的提示，logcat也没有看到蓝色的调用栈log，这样的闪退最是蛋疼了，还好必现。复现几次之后，终于从logcat中看到了一行可疑的log：A/Looper: Could not create epoll instance. errno=24，看起来又是在native层闪退了。本文就把这个问题的分析解决过程记录了下来。 方法论 遇见没...
too many open files
yanghuidang
08-18 270
http://langyu.iteye.com/blog/763247 运行在Linux系统上的Java程序可能会出现"Too many open files"的异常情况，且常见于高并发访问文件系统，多线程网络连接等场景。 程序经常访问的文件、socket在Linux中都是文件file，系统需要记录每个当前访问file的name、location、access authorit...
Too many open files错误
weixin_34054866的博客
11-20 236
1、现象启动tomcat程序报错：Too many open files Caused by: java.io.IOException: Too many open files at sun.nio.ch.EPollArrayWrapper.epollCreate(Native Method) at sun.nio.ch.EPollArrayWrapper.<init>...
epoll/linux支持的最大连接数,文件描述符不够报错信息是too many open files的解决办法
qq160816的专栏
07-28 1780
epoll/linux支持的最大连接数,文件描述符不够报错信息是too many open files的解决办法： ulimit -n 1048576
failed to create fsnotify watcher: too many open files
最新发布
08-10
当您遇到 "failed to create fsnotify watcher: too many open files" 错误时，它通常意味着操作系统限制了单个进程可以打开的文件描述符的最大数量，而您的程序试图创建过多的文件监控（fsnotify）watcher。...
epoll4:第四代epoll协程相结合的网络库
03-17
大大降低系统开发难度），再一个对第三方库的调用不应该用hook方式，因为这种方式鬼才知道有没有问题，其实解决这个故我使用boost.Coroutine2这个库，封装了epoll系统调用，让c ++也能愉快的使用协程来开发后台服务...
由一个EPOLLET模式accept()问题引起对TCP连接的回顾
kapuchang的博客
01-20 922
问题起因 在生产环境出现一个TCP网络连接的异常，socket accept()时返回错误，错误码errno=24，strerror=”Too many open files”，线程占用CPU接近100%，即死循环。查明直接原因是，进程的open files数量太小，当连接数超时该数目时即会返回上述错误。（这要提醒一句：要注意父子进程的limits参数，也许系统配置参数已修改，但父进程是在修改前启...
too many open files(打开的文件过多)解决方法
热门推荐
muzlei的博客
11-08 2万+
https://www.cnblogs.com/conanwang/p/5818441.html SU: failed to execute /bin/bash:系统中打开的文件过多 一、产生原因 too many open files(打开的文件过多)是Linux系统中常见的错误，从字面意思上看就是说程序打开的文件数过多，不过这里的files不单是文件的意思，也包括打开的通讯链接(比如sock...
Monitor项目开发走过的路~子线程Toast全解析
qinlong275的博客
12-01 424
Toast在Android开发中是很常用的，可以很便捷清楚的反映给用户一些重要的实时信息。在Monitor项目开发中在Toast的使用上也是遇到了一些问题。平时最经常用的方法就是在Activity中调用Toast.makeText().show()方法，我们需要传入当前的上下文环境，通常传入当前的Activity.this即可。可是项目中与服务器端交互的代码是我们后端开发人员写的，他让我将里面的日志
java.io.IOException: error=24, 打开的文件过多
anjing900812的博客
11-23 4684
开发的hadoop-consumer程序周期性重启，在程序运行日志中也找不到异常。后来才发现是因为： 1、try catch中使用e.printStackTrace()，本以为出现异常时会打印日志。但程序的日志直接输出至屏幕，然后写了一个shell脚本将其重定向至一个文件，郁闷的是异常信息并没有写入日志文件中，所以发现不了这个错误； 2、在catch中增加了system.out.print
Unable to create application data OkHttp崩溃bug
zhjali123的专栏
09-03 2574
遇到的错误 结论 页面存在过多的 https 请求，每次申请ssl资源时，创建一个pipe，最后耗光了 可打开文件描述符的数量 需要明确下 页面的https 资源消耗情况 原因 直接崩溃Log E NativeCrypto: AppData::create pipe(2) failed: Too many open files native资源被耗尽(FileDescriptor)，导致pipe 打开文件出问题OkHttp issue 类似案例 可能导致其他问题 1.AppData::create
Could not read input channel file descriptors from parce问题分析解决
为码消得人憔悴
06-05 7811
最近项目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...
Android应用程序消息循环
lsdmx2016的总结
12-19 3259
Android应用程序的消息处理框架，是通过 Looper,Handler,MessageQueue,这三个类实现的，Looper 是一个消息循环，它维护着一个MessageQueue，Looper 是和某个线程相关的，Handler 也是和线程相关的，一个Looper 对应着一个Handler,Handler 就是用来发送和处理与它相关的线程的消息队列的消息的。    Android应用程序在
Android笔记 跟踪c++代码报错
reasonboy的博客
10-26 1864
问题 用logcat抓取到报错如下 10-26 15:14:46.777 3174 3174 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone 10-26 15:14:46.778 1810 1810 I /system/bin/tombstoned: received cr...
[Python] Native Crash Addr2line 自动解析Tombstone文件脚本
TaylorPotter的博客
01-17 1921
[Python] Native Crash Addr2line 自动解析Tombstone文件脚本 使用方法 1.解析单个tombstone文件： python ./as_tomba.py tombstone_file_path symbol_root_path 在tombstone_file_path目录下生成 tombstone文件名_pid_pname.out 的解析之后文件 2.批量解析...
python OSError: [Errno 24] Too many open files
笑笑布丁的博客
01-14 6733
背景：scrapy启动了多个爬虫，每个爬虫都有读写文件的pipeline。发生了这一问题. 原因：超出了进程同一时间最多可开启的文件数. 解决办法： ulimit -n 2048，将数目提高，mac默认是256，linux是1024，自行体会. ...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值