处理图片（Process pictures）.docVIP

处理图片（Process pictures） Apr Android application development (you must know, avoid memory overflow picture processing scheme) Today to share some pictures commonly used technical solutions, Android application development friends must understand it! As we all know, in Android application development, when dealing with pictures, a little careless will lead to the following abnormalities: Java.lang.OutofMemoryError:, bitmap, size, exceeds, VM, budget. The following are the reasons for caution when loading Bitmap: Typically, mobile devices have limited system resources, and Android devices allocate 16M of memory space to each application. Section 3.7 of the Android compatibility definition file (CDD). Provides various screen sizes and densities required for the compatibility of virtual machines and the memory of the lowest application. The optimized application should refer to this minimum memory limit. However, many vendors of Android device systems will have higher limits on configuration. Bitmap will take up a lot of memory, especially with rich image applications such as photo management. For example, in the Galaxy Nexus camera, the highest picture taken is 2592x1936 pixels (5 million pixels). If you use the bitmap configuration (default is ARGB_8888 from Android2.3), then the image is loaded into memory requires approximately 19MB of memory (2592*1936*4 bytes), will run the application immediately on some devices memory lead to abnormal occurrence. The Android application UI often needs to load multiple images at a time. As in ListView, GridView, and ViewPager, usually in one screen, including multiple pictures. How to load images efficiently Pictures vary in size and size. In most cases, it is greater than the size of the image that the user wants to use in the application. For example, when managing camera shots in a systems Gallery application, the size of the picture is often larger than the density of the screen. Based on memory limitations, ideally you need to