2013-04-17 29 views
0

任何人都可以向我解釋此LogCat輸出以及如何解決它?我正在用我的手機(Samsung Galaxy Nexus)測試我的Android應用程序,就像那樣;系統強制拘留和在logcat的印刷本...Android應用程序中的OutOfMemoryError

04-17 09:43:09.189: E/AndroidRuntime(1194): FATAL EXCEPTION: main 
04-17 09:43:09.189: E/AndroidRuntime(1194): java.lang.OutOfMemoryError 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.graphics.BitmapFactory.nativeDecodeStream(Native Method) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:527) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.graphics.BitmapFactory.decodeFile(BitmapFactory.java:301) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.graphics.BitmapFactory.decodeFile(BitmapFactory.java:326) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.graphics.drawable.Drawable.createFromPath(Drawable.java:894) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.ImageView.resolveUri(ImageView.java:638) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.ImageView.setImageURI(ImageView.java:379) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at tian.proto.galeriaImagenes$ImageAdapter.getView(galeriaImagenes.java:169) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.AbsSpinner.onMeasure(AbsSpinner.java:193) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.View.measure(View.java:15172) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1390) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.LinearLayout.measureVertical(LinearLayout.java:681) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.LinearLayout.onMeasure(LinearLayout.java:574) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.View.measure(View.java:15172) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.FrameLayout.onMeasure(FrameLayout.java:310) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.View.measure(View.java:15172) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.LinearLayout.measureVertical(LinearLayout.java:833) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.LinearLayout.onMeasure(LinearLayout.java:574) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.View.measure(View.java:15172) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:4816) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.widget.FrameLayout.onMeasure(FrameLayout.java:310) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2148) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.View.measure(View.java:15172) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:1850) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1102) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1275) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1000) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:4214) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.Choreographer$CallbackRecord.run(Choreographer.java:725) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.Choreographer.doCallbacks(Choreographer.java:555) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.Choreographer.doFrame(Choreographer.java:525) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:711) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.os.Handler.handleCallback(Handler.java:615) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.os.Handler.dispatchMessage(Handler.java:92) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.os.Looper.loop(Looper.java:137) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at android.app.ActivityThread.main(ActivityThread.java:4899) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at java.lang.reflect.Method.invokeNative(Native Method) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at java.lang.reflect.Method.invoke(Method.java:511) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558) 
04-17 09:43:09.189: E/AndroidRuntime(1194):  at dalvik.system.NativeStart.main(Native Method) 

回答

0

如果你在運行時加載的位圖,您可以根據您使用this technique設備讀取其規模下來。如果您從res目錄加載它,則可能需要使用圖像編輯器將其縮小。無論哪種方式,圖像顯然太大,不適合內存。

0

正如我所看到的,您使用ImageView.setImageURI加載圖像。

現在很多圖像,尤其是高分辨率相機(或手機)所拍攝的圖像,很容易佔據比在屏幕上顯示它們所需的空間更多的空間。

當您嘗試直接將它們加載到位圖中時,您的應用程序將耗盡內存並崩潰。 另請參閱question或@oakleaf關於使用大型位圖的Android Developer Training鏈接的答案。

相關問題