2012-05-09 63 views
2

我试着写一些相机意向处理程序,拍照和后旋进他们(如果需要)。如果我在高分辨率拍摄一些照片,我的程序中断“分配过大”。如果我采取一些较低的分辨率我能够采取更多,但它也会打破。经过一番搜索后,我发现我必须回收位图,而且我已经制作了手册。但问题并没有消失。我的主要问题是,我不知道是否有1.在我的代码2.内存泄漏我不知道为什么它试图分配momory因为我没有表现出我的PROGRAMM位图(现在) ,我只是将它们保存起来以备后用。内存泄漏而位图处理

public void onClick(View view) { 
    Intent i = new Intent("android.media.action.IMAGE_CAPTURE"); 
    this.mLastPic = new File(this.mFs.getDirPath(), this.mFs.getNextPicName()); //create and save a file for pic 
    i.putExtra(MediaStore.EXTRA_OUTPUT, Uri.fromFile(this.mLastPic)); 
    this.startActivityForResult(i, 0); 
} 

上activty结果处理

public void onActivityResult(int requestCode, int resultCode, Intent data) { 
    super.onActivityResult(requestCode, resultCode, data); 
    if(resultCode == Activity.RESULT_OK && requestCode == 0) { 

     try { 
      if(!this.mController.getSetting(R.string.USE_HEIGH_RESOLUTION)) { //use high res or not 
       int quality = this.mFs.getPicQuality(); //get compress quality 
       Bitmap pic = BitmapFactory.decodeFile(this.mLastPic.getPath()); 
       ByteArrayOutputStream outStream = new ByteArrayOutputStream(); 
       pic.compress(Bitmap.CompressFormat.JPEG, quality, outStream); 
       String path = this.mLastPic.getPath(); 
       if(this.mLastPic.delete()) { //replace the old file with a now file 
        File newFile = new File(path); 
        newFile.createNewFile(); 
        FileOutputStream os = new FileOutputStream(newFile); 
        os.write(outStream.toByteArray()); 
        Log.d("newEntryActivity.onActivityResult", "replaced pic "); 
       } else { 
        Log.d("newEntryActivity.onActivityResult", "cant delete old pic"); 
       } 
       pic.recycle(); //cleaning up 
       outStream.close(); 
      } 
     } catch (IOException e) { 
      e.printStackTrace(); 
     } 
    } 

} 

logcat的显示

05-09 14:35:01.694: E/dalvikvm-heap(845): 6380496-byte external allocation too large for this process. 05-09 14:35:01.694: E/(845): VM won't let us allocate 6380496 bytes

05-09 14:35:01.694: D/AndroidRuntime(845): Shutting down VM

05-09 14:35:01.694: W/dalvikvm(845): threadid=3: thread exiting with uncaught exception (group=0x4001b188)

05-09 14:35:01.694: E/AndroidRuntime(845): Uncaught handler: thread main exiting due to uncaught exception

05-09 14:35:01.714: E/AndroidRuntime(845): java.lang.RuntimeException: Unable to start activity ComponentInfo{unicorn.Heurazio/unicorn.Heurazio.SettingsActivity}: android.view.InflateException: Binary XML file line #2: Error inflating class ...

05-09 14:35:01.714: E/AndroidRuntime(845): Caused by: android.view.InflateException: Binary XML file line #2: Error inflating class

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.LayoutInflater.createView(LayoutInflater.java:513)

05-09 14:35:01.714: E/AndroidRuntime(845): at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:563)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.LayoutInflater.inflate(LayoutInflater.java:385)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.LayoutInflater.inflate(LayoutInflater.java:320)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.LayoutInflater.inflate(LayoutInflater.java:276)

05-09 14:35:01.714: E/AndroidRuntime(845): at com.android.internal.policy.impl.PhoneWindow.setContentView(PhoneWindow.java:198)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.app.Activity.setContentView(Activity.java:1622)

05-09 14:35:01.714: E/AndroidRuntime(845): at unicorn.Heurazio.SettingsActivity.onCreate(SettingsActivity.java:38)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2459)

05-09 14:35:01.714: E/AndroidRuntime(845): ... 11 more

05-09 14:35:01.714: E/AndroidRuntime(845): Caused by: java.lang.reflect.InvocationTargetException

05-09 14:35:01.714: E/AndroidRuntime(845): at android.widget.LinearLayout.(LinearLayout.java:92)

05-09 14:35:01.714: E/AndroidRuntime(845): at java.lang.reflect.Constructor.constructNative(Native Method)

05-09 14:35:01.714: E/AndroidRuntime(845): at java.lang.reflect.Constructor.newInstance(Constructor.java:446)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.LayoutInflater.createView(LayoutInflater.java:500)

05-09 14:35:01.714: E/AndroidRuntime(845): ... 21 more

05-09 14:35:01.714: E/AndroidRuntime(845): Caused by: java.lang.OutOfMemoryError: bitmap size exceeds VM budget

05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.Bitmap.nativeCreate(Native Method) > 05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.Bitmap.createBitmap(Bitmap.java:468)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.Bitmap.createBitmap(Bitmap.java:435)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.Bitmap.createScaledBitmap(Bitmap.java:340)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.BitmapFactory.finishDecode(BitmapFactory.java:488)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:462)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:323)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:697)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.content.res.Resources.loadDrawable(Resources.java:1705)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.content.res.TypedArray.getDrawable(TypedArray.java:548)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.View.(View.java:1850)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.View.(View.java:1799)

05-09 14:35:01.714: E/AndroidRuntime(845): at android.view.ViewGroup.(ViewGroup.java:284)

任何帮助将是巨大的。

问候亚历

+0

编辑:我忘了说,当我回到privios活动和/或启动其他意图出现问题。 – Alex

回答

0

我的程序的一些阅读和修改后,就像在重载应用程序添加到背景参考,抹所有不需要的背景元素我还有同样的问题,这似乎是甚至沃瑟。

如果我能相信我的计算为位图

Bitmap tmp = BitmapFactory.decodeResource(this.getResources(), R.drawable.logo); 
Log.d("mainApp", tmp.getRowBytes() * tmp.getHeight()/1024 + "kB"); 

100kB标志(巴纽)的大小需要6mB RAM(这将适合异常消息)。任何想法都会很棒。

+1

OK,finaly我发现的bug。在MAT的帮助下,我能够弄清楚,我有两个引用长期运行的上下文。 – Alex

-3

尝试在你的清单中添加应用程序android:largeHeap="true"

+0

dosn't这只是推回问题? – Alex

+0

这不是处理内存泄漏的正确方法。 – sdasdadas

1

如果你检查你的日志,它看起来像充气的同时在unicorn.Heurazio.SettingsActivity视图出现大(〜6MB)位分配。检查您的资源,看看您是否在某处使用大型位图作为背景。

+0

我在每个活动中都有背景图片。它的大小约为75kB。它作为背景图像放置在布局中。 diden't android管理'em的创建和回收? – Alex

+1

文件大小并不总是与内存大小相同,尤其是如果它是JPG。是的,Android应该创建/回收/释放它们,但有时并不是很擅长及时完成它,并且您需要手动解除视图以帮助提示它。 – kabuko

+0

我如何解除视图? sry为那noobie问题... – Alex