Android致命讯号11(Android Fatal Signal 11)
在我在Android上开发的应用程序中,我不断收到致命信号11错误。
我认为这是与我正在访问内存的方式有关,但我无法弄清楚是什么导致的。
任何帮助将不胜感激!
这是LogCat:
05-02 23:47:17.618: D/dalvikvm(590): GC_FOR_ALLOC freed 68K, 4% free 6531K/6787K, paused 101ms
05-02 23:47:17.638: I/dalvikvm-heap(590): Grow heap (frag case) to 7.619MB for 1228816-byte allocation
05-02 23:47:17.738: D/dalvikvm(590): GC_CONCURRENT freed 1K, 4% free 7730K/8007K, paused 5ms+14ms
05-02 23:47:17.878: D/dalvikvm(590): GC_FOR_ALLOC freed <1K, 4% free 7730K/8007K, paused 37ms
05-02 23:47:17.888: I/dalvikvm-heap(590): Grow heap (frag case) to 8.790MB for 1228816-byte allocation
05-02 23:47:17.998: D/dalvikvm(590): GC_CONCURRENT freed <1K, 4% free 8930K/9223K, paused 4ms+4ms
05-02 23:47:17.998: A/libc(590): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
In the app I'm developing on Android, I keep getting a Fatal Signal 11 error.
I think it's something to do with the way that I'm accessing the memory but I can't figure out what is causing it.
Any help will be much appreciated!
Here's the LogCat:
05-02 23:47:17.618: D/dalvikvm(590): GC_FOR_ALLOC freed 68K, 4% free 6531K/6787K, paused 101ms
05-02 23:47:17.638: I/dalvikvm-heap(590): Grow heap (frag case) to 7.619MB for 1228816-byte allocation
05-02 23:47:17.738: D/dalvikvm(590): GC_CONCURRENT freed 1K, 4% free 7730K/8007K, paused 5ms+14ms
05-02 23:47:17.878: D/dalvikvm(590): GC_FOR_ALLOC freed <1K, 4% free 7730K/8007K, paused 37ms
05-02 23:47:17.888: I/dalvikvm-heap(590): Grow heap (frag case) to 8.790MB for 1228816-byte allocation
05-02 23:47:17.998: D/dalvikvm(590): GC_CONCURRENT freed <1K, 4% free 8930K/9223K, paused 4ms+4ms
05-02 23:47:17.998: A/libc(590): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1)
原文:https://stackoverflow.com/questions/10423128
更新时间:2019-09-07 03:56
最满意答案
我一直在尝试将另一个Class中的未初始化的Canvas调用,因此当它尝试获取其高度或宽度时,会崩溃。
I had been trying to call an uninitialised Canvas inside another Class so when it was trying to get the height or width of it, it would crash.
2012-05-03
相关问答
如果更改的标志为false,则不会在第二个布局过程中进行渲染,以解决此问题。 Not rendering on the second layout pass if the changed flag is false solved this issue for me.
我一直在尝试将另一个Class中的未初始化的Canvas调用,因此当它尝试获取其高度或宽度时,会崩溃。 I had been trying to call an uninitialised Canvas inside another Class so when it was trying to get the height or width of it, it would crash.
我也遇到了这个问题。 但是,对我来说, close()不是原因。 问题是close()后访问套接字。 特别是,在套接字关闭之后,对套接字输入流的available()调用导致了段错误。 I ran into this problem as well. However, for me close() was not the cause. The problem was accessing the socket after close(). Specifically, the call to avai
...
确保你已经将所有的权限和遥测服务放置在清单中。 除此之外,还要确保你在课堂上包含了正确的输入。 E/OfflineManager(3182): Failed to read the storage key: null
提供线索说明您可能正在使用离线? 你可以发布一些代码,你的gradle文件看起来很好。 Make sure you've placed all the permissions and telemetry service within your manifest. Other the
...
好的,我发现了问题。 这与我在网上发布的片段无关。 我有一个额外的函数storeSVM( CvSVM svm) ,它已被弃用但仍然被调用(它基本上什么也没做了)。 一旦我删除了呼叫,我的代码就可以了。 Okay, I found the problem. It was unrelated to the snippets I posted online. I had an extra function storeSVM( CvSVM svm), which was deprecated but st
...
我收到错误是因为我将错误的参数传递给PortSIP库的方法,所以因为这个库引发了错误。 I was getting the error because I was passing wrong argument to a method of the PortSIP library, so because of that the library was throwing error.
当TextureView失去可见性时(或者因为屏幕旋转,其他Activity出现在前面或者您按下Home按钮),它会使其SurfaceTexture.OnFrameAvailableListener (在GrepCode上 ) 失效 。 它看起来像是在发生这种情况时, Canvas实例在C ++代码本身执行drawX()方法时,应用程序将崩溃,因为在某些原因下,包含该画布的内存在方法完成之前被清除。 但是,由于Canvas.drawX()方法使用Android本机C ++代码,因此C ++不会抛出
...
我已修复了我的问题,我的代码不再提供任何错误,我的应用程序不再崩溃。 实际上,代码的逻辑正在发挥作用。 仍然需要添加/更改某些功能,但这些功能与我在此处提到的问题无关。 编辑:我的代码更改(可能)修复它包括正确设置/获取calcSum中循环的最大值,使用双变量来存储双结果而不是int(在C ++代码中的某个地方),并且可能是其他变化。 我意识到的另一件事是我的代码只是在括号内计算表达式,这不是程序的错,故障在于我对代码逻辑的假设。 简介:如果在这种情况下发生此错误,您可能需要修复代码,该程序在技术
...
嗨我有类似的问题 。 我的问题是由OkHTTP的SSL管理引起的。 在OkHTTP的github页面上查看这个bug问题 我的解决方法(他们说它将用v2.0修复)是这样的: URL.setURLStreamHandlerFactory(new OkHttpClient());
更新:Square发布了OkHTTP v1.5.0,他们应该修复了SSL问题。 想要将全局SSL上下文与OkHttp一起使用的应用程序应使用以下内容配置其OkHttpClient实例: okHttpClient.setSs
...
问题可能是,当您创建新页面时,您必须重新初始化/获取Canvas 。 Canvas canvas = page.getCanvas();
The problem is probably, that when you are creating a new page, you have to re-initialize / get the Canvas again. Canvas canvas = page.getCanvas();