- html - 出于某种原因,IE8 对我的 Sass 文件中继承的 html5 CSS 不友好?
- JMeter 在响应断言中使用 span 标签的问题
- html - 在 :hover and :active? 上具有不同效果的 CSS 动画
- html - 相对于居中的 html 内容固定的 CSS 重复背景?
我的背景图像太大,因此应用程序崩溃并出现以下错误(我也从 LogCat 复制其他有用的消息)
01-10 14:53:48.799: E/dalvikvm-heap(9297): Out of memory on a 6955024-byte allocation.
01-10 14:53:48.799: I/dalvikvm(9297): "main" prio=5 tid=1 RUNNABLE
01-10 14:53:48.799: I/dalvikvm(9297): | group="main" sCount=0 dsCount=0 obj=0x40a729a0 self=0x2a00bba8
01-10 14:53:48.799: I/dalvikvm(9297): | sysTid=9297 nice=0 sched=0/0 cgrp=apps handle=1073849308
01-10 14:53:48.812: I/dalvikvm(9297): | state=R schedstat=( 38497557466 45560972992 4658 ) utm=3335 stm=514 core=0
01-10 14:53:48.840: I/dalvikvm(9297): at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)
01-10 14:53:48.840: I/dalvikvm(9297): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:502)
01-10 14:53:48.840: I/dalvikvm(9297): at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:355)
01-10 14:53:48.840: I/dalvikvm(9297): at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:785)
01-10 14:53:48.840: I/dalvikvm(9297): at android.content.res.Resources.loadDrawable(Resources.java:1965)
01-10 14:53:48.840: I/dalvikvm(9297): at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
01-10 14:53:48.840: I/dalvikvm(9297): at android.view.View.<init>(View.java:3330)
01-10 14:53:48.860: I/dalvikvm(9297): at android.view.View.<init>(View.java:3259)
01-10 14:53:48.860: I/dalvikvm(9297): at android.view.ViewGroup.<init>(ViewGroup.java:425)
01-10 14:53:48.860: I/dalvikvm(9297): at android.widget.RelativeLayout.<init>(RelativeLayout.java:210)
01-10 14:53:48.860: I/dalvikvm(9297): at java.lang.reflect.Constructor.constructNative(Native Method)
01-10 14:53:48.860: I/dalvikvm(9297): at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
01-10 14:53:48.860: I/dalvikvm(9297): at android.view.LayoutInflater.createView(LayoutInflater.java:587)
01-10 14:53:48.860: I/dalvikvm(9297): at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
01-10 14:53:48.860: I/dalvikvm(9297): at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
01-10 14:53:48.860: I/dalvikvm(9297): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
01-10 14:53:48.860: I/dalvikvm(9297): at android.view.LayoutInflater.inflate(LayoutInflater.java:466)
01-10 14:53:48.860: I/dalvikvm(9297): at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
01-10 14:53:48.860: I/dalvikvm(9297): at com.xxx.xxx.InputFragment.onCreateView(InputFragment.java:70)
01-10 14:53:48.860: I/dalvikvm(9297): at android.support.v4.app.Fragment.performCreateView(Fragment.java:1478)
01-10 14:53:48.860: I/dalvikvm(9297): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:927)
01-10 14:53:48.860: I/dalvikvm(9297): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1104)
01-10 14:53:48.860: I/dalvikvm(9297): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1086)
01-10 14:53:48.860: I/dalvikvm(9297): at android.support.v4.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:1877)
01-10 14:53:48.860: I/dalvikvm(9297): at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:552)
01-10 14:53:48.860: I/dalvikvm(9297): at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1164)
01-10 14:53:48.860: I/dalvikvm(9297): at android.app.Activity.performStart(Activity.java:5114)
01-10 14:53:48.860: I/dalvikvm(9297): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2153)
01-10 14:53:48.860: I/dalvikvm(9297): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2230)
01-10 14:53:48.860: I/dalvikvm(9297): at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:3692)
01-10 14:53:48.860: I/dalvikvm(9297): at android.app.ActivityThread.access$700(ActivityThread.java:141)
01-10 14:53:48.860: I/dalvikvm(9297): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1240)
01-10 14:53:48.910: I/dalvikvm(9297): at android.os.Handler.dispatchMessage(Handler.java:99)
01-10 14:53:48.910: I/dalvikvm(9297): at android.os.Looper.loop(Looper.java:137)
01-10 14:53:48.920: I/dalvikvm(9297): at android.app.ActivityThread.main(ActivityThread.java:5041)
01-10 14:53:48.920: I/dalvikvm(9297): at java.lang.reflect.Method.invokeNative(Native Method)
01-10 14:53:48.920: I/dalvikvm(9297): at java.lang.reflect.Method.invoke(Method.java:511)
01-10 14:53:48.920: I/dalvikvm(9297): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
01-10 14:53:48.920: I/dalvikvm(9297): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
01-10 14:53:48.920: I/dalvikvm(9297): at dalvik.system.NativeStart.main(Native Method)
01-10 14:53:49.315: D/skia(9297): --- decoder->decode returned false
01-10 14:53:49.315: D/AndroidRuntime(9297): Shutting down VM
01-10 14:53:49.320: W/dalvikvm(9297): threadid=1: thread exiting with uncaught exception (group=0x40a71930)
01-10 14:53:49.570: E/AndroidRuntime(9297): FATAL EXCEPTION: main
01-10 14:53:49.570: E/AndroidRuntime(9297): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.xxx.xxx/com.xxx.xxx.MainActivity}: android.view.InflateException: Binary XML file line #1: Error inflating class <unknown>
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2180)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2230)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.ActivityThread.handleRelaunchActivity(ActivityThread.java:3692)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.ActivityThread.access$700(ActivityThread.java:141)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1240)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.os.Handler.dispatchMessage(Handler.java:99)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.os.Looper.loop(Looper.java:137)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.ActivityThread.main(ActivityThread.java:5041)
01-10 14:53:49.570: E/AndroidRuntime(9297): at java.lang.reflect.Method.invokeNative(Native Method)
01-10 14:53:49.570: E/AndroidRuntime(9297): at java.lang.reflect.Method.invoke(Method.java:511)
01-10 14:53:49.570: E/AndroidRuntime(9297): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:793)
01-10 14:53:49.570: E/AndroidRuntime(9297): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:560)
01-10 14:53:49.570: E/AndroidRuntime(9297): at dalvik.system.NativeStart.main(Native Method)
01-10 14:53:49.570: E/AndroidRuntime(9297): Caused by: android.view.InflateException: Binary XML file line #1: Error inflating class <unknown>
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.LayoutInflater.createView(LayoutInflater.java:613)
01-10 14:53:49.570: E/AndroidRuntime(9297): at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.LayoutInflater.inflate(LayoutInflater.java:466)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.LayoutInflater.inflate(LayoutInflater.java:396)
01-10 14:53:49.570: E/AndroidRuntime(9297): at com.xxx.xxx.InputFragment.onCreateView(InputFragment.java:70)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.support.v4.app.Fragment.performCreateView(Fragment.java:1478)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:927)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1104)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.support.v4.app.FragmentManagerImpl.moveToState(FragmentManager.java:1086)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.support.v4.app.FragmentManagerImpl.dispatchActivityCreated(FragmentManager.java:1877)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:552)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1164)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.Activity.performStart(Activity.java:5114)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2153)
01-10 14:53:49.570: E/AndroidRuntime(9297): ... 12 more
01-10 14:53:49.570: E/AndroidRuntime(9297): Caused by: java.lang.reflect.InvocationTargetException
01-10 14:53:49.570: E/AndroidRuntime(9297): at java.lang.reflect.Constructor.constructNative(Native Method)
01-10 14:53:49.570: E/AndroidRuntime(9297): at java.lang.reflect.Constructor.newInstance(Constructor.java:417)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.LayoutInflater.createView(LayoutInflater.java:587)
01-10 14:53:49.570: E/AndroidRuntime(9297): ... 27 more
01-10 14:53:49.570: E/AndroidRuntime(9297): Caused by: java.lang.OutOfMemoryError
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:502)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:355)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:785)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.content.res.Resources.loadDrawable(Resources.java:1965)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.content.res.TypedArray.getDrawable(TypedArray.java:601)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.View.<init>(View.java:3330)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.View.<init>(View.java:3259)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.view.ViewGroup.<init>(ViewGroup.java:425)
01-10 14:53:49.570: E/AndroidRuntime(9297): at android.widget.RelativeLayout.<init>(RelativeLayout.java:210)
01-10 14:53:49.570: E/AndroidRuntime(9297): ... 30 more
我的背景图像位于 Drawable 文件夹中。是的,我的意思是“文件夹”,因为该应用程序旨在支持多个屏幕,并且图像位于所有文件夹中,尺寸略有变化。
如何才能毫无问题地加载这么大的位图?我执行了以下代码。
public static Bitmap getResizedBitmap(Bitmap image, int newHeight, int newWidth) {
int width = image.getWidth();
int height = image.getHeight();
float scaleWidth = ((float) newWidth) / width;
float scaleHeight = ((float) newHeight) / height;
// create a matrix for the manipulation
Matrix matrix = new Matrix();
// resize the bit map
matrix.postScale(scaleWidth, scaleHeight);
// recreate the new Bitmap
Bitmap resizedBitmap = Bitmap.createBitmap(image, 0, 0, width, height,
matrix, false);
return resizedBitmap;
}
但实际情况是,这段代码是手动设置宽度和高度的,对吗?但我要应用此图像作为背景图像,所以我不知道这是否是最好的方法,并且我不确定要插入什么值作为宽度和高度。我所知道的是我需要在 onCreateView()
方法中设置图像(我正在使用 fragment )。
最佳答案
在加载图像之前使用 BitmapFactory.Options 获取图像的大小,然后您可以根据需要将背景缩小到较低分辨率的图像,该图像仍然适合背景但不会引发 OOM 错误。此外,您还可以将 DisplayMetrics 用于您所需的宽度和高度,或者您要设置背景的 View 的宽度和高度。
来自 Android 培训文档 ( http://developer.android.com/training/displaying-bitmaps/load-bitmap.html ):
The BitmapFactory class provides several decoding methods (decodeByteArray(), decodeFile(), decodeResource(), etc.) for creating a Bitmap from various sources. Choose the most appropriate decode method based on your image data source. These methods attempt to allocate memory for the constructed bitmap and therefore can easily result in an OutOfMemory exception. Each type of decode method has additional signatures that let you specify decoding options via the BitmapFactory.Options class. Setting the inJustDecodeBounds property to true while decoding avoids memory allocation, returning null for the bitmap object but setting outWidth, outHeight and outMimeType. This technique allows you to read the dimensions and type of the image data prior to construction (and memory allocation) of the bitmap.
BitmapFactory.Options options = new BitmapFactory.Options();
options.inJustDecodeBounds = true;
BitmapFactory.decodeResource(getResources(), R.id.myimage, options);
int imageHeight = options.outHeight;
int imageWidth = options.outWidth;
String imageType = options.outMimeType;
To avoid java.lang.OutOfMemory exceptions, check the dimensions of a bitmap before decoding it, unless you absolutely trust the source to provide you with predictably sized image data that comfortably fits within the available memory.
关于java - 图片太大 : OutOfMemory Exception,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/21047721/
这个问题在这里已经有了答案: Python try...except comma vs 'as' in except (5 个回答) 关闭7年前。 在python中,有两种方法可以捕获异常 excep
在 Java 中,我有一个从 Exception 扩展的异常类,但是每当我抛出它时,编译器都会说它需要被捕获/必须声明方法 throws异常。 当我使用从 Exception 扩展的 RuntimeE
我有一组用户、组以及用户和组之间的映射。我有各种操作这些集合的函数,但是不能为不存在的用户添加用户组映射,也不能删除仍然有用户作为成员的组等。 所以基本上我希望这些函数抛出必须由调用者明确处理的“异常
我正在尝试使用上载控件上载20兆的文件,并且在Visual Studio的内置Web服务器上可以正常工作,但是一旦将其发布到生产服务器(我无权访问),我总是收到以下错误消息: Server Error
我想断言运行某些代码时会引发特定异常(SSLHandshakeException)。 assertThatThrownBy(() -> { // some code }).is
这个问题我暂时解决不了。我很乐意提供一些建议。 当我尝试抛出异常时(我自己创建了一个 Java 风格的异常) throw Exception (); 编译器提出抗议: DataTypes/Date.c
我有以下文件: from fabric.api import env, execute, run env.hosts = ['1.2.3.4'] def taskA(): run('ls')
我正在阅读一些包含类似于以下功能的源代码: def dummy_function(): try: g = 1/0 except Exception as e:
根据标准 ML 的定义(修订版): The idea is that dynamic evaluation of a non-expansive expression will neither gen
当 GHCi 在运行时发现调用产生的值与函数的模式匹配不匹配时,有没有办法让 GHCi 产生更好的异常消息? 它目前给出了产生非详尽模式匹配的函数的行号,虽然有时会有所帮助,但确实需要一轮调试,有时我
我有一个最佳实践问题。我意识到这是主观的,但想问问比我更聪明的人,这是否是一种常见的编程实践。 如果您有一种不希望干扰应用程序重要功能的非关键方法,那么使用这样的错误接收器是否常见? Try
在编程中,异常是否总是错误(被零除,访问冲突等等)? 如果不是,您能否提供不是错误的异常示例? 谢谢。 最佳答案 异常通常用于管理错误,它们使错误处理更加容易,但它们并不总是错误。 任何需要单独代码路
我很想知道 OCaml 运行时如何处理异常以使它们如此轻量。他们是使用 setjmp/longjmp 还是在每个函数中返回一个特殊值并传播它? 在我看来,longjmp会给系统带来一点压力,但只有在引
在我的 C# 代码中,我可以访问 MyNamespace.Exception 以及 System.Exception。当我想捕获其中一个异常时,理想情况下我会完全限定要捕获的异常或使用别名来明确说明。
我正在使用 Visual C++ 2005 Express Edition 并遇到以下链接器错误: 19>mylib1.lib(mylibsource1.obj) : error LNK2019: u
这个问题在这里已经有了答案: Is there "Break on Exception" in IntelliJ? (6 个回答) 关闭7年前。 我想在调试器中运行我的测试套件并中断任何意外异常,但是
Like in this picture 我知道它们都可以正常工作,但我只是想知道它们之间有何不同? PS:我是初学者。 最佳答案 A LogEvent可以同时包含消息和异常。如果您使用第一种形式:
我知道避免 Doctrine 上的异常似乎是一种奇怪的行为,但我需要这样做,因为我在一个旧项目中工作,过去有人执行了一些迁移,然后他决定删除它,所以现在复制起来很复杂本地生产环境没有崩溃,这就是为什么
我想创建一个名为 SecurityException 的新异常。 我应该把代码放在哪里? class SecurityException extends CakeException {}; 谢谢! 最
我一直在使用throw new Exception("...")在我的代码中,因为我找不到其他可以使用的东西。我正在寻找像 C++'s 这样的东西 out_of_range 和 logic_error
我是一名优秀的程序员,十分优秀!