Android 致命信号 11

问题描述

在我正在 Android 上开发的应用程序中，我不断收到致命信号 11 错误.

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.

任何帮助将不胜感激！

这是 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)

推荐答案

我一直试图在另一个 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.

这篇关于Android 致命信号 11的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持跟版网！