【发布时间】:2019-12-26 04:34:05
【问题描述】:
我在我的应用程序中启用了strict mode,但它因错误而崩溃
boolean DEVELOPER_MODE=true;
if (DEVELOPER_MODE) {
StrictMode.setThreadPolicy(new StrictMode.ThreadPolicy.Builder()
.detectDiskReads()
.detectDiskWrites()
.detectAll() // or .detectAll() for all detectable problems //.detectNetwork()
.penaltyLog()
.build());
StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder()
.detectLeakedSqlLiteObjects()
.detectLeakedClosableObjects()
.penaltyLog()
.penaltyDeath()
.build());
}
E/StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.java.lang.Throwable: Explicit termination method 'close' not called
一行
private void getRecentImages (){
String[] colums={MediaStore.Images.Media.DATA,MediaStore.Images.Media._ID};
Cursor imageCursor = getActivity().getContentResolver().query(
MediaStore.Images.Media.EXTERNAL_CONTENT_URI,
colums,
null,
null,
MediaStore.Images.Media._ID);
int image_Column_Index=imageCursor.getColumnIndex(MediaStore.Images.Media._ID);
count=imageCursor.getCount();
thumbnails=new Bitmap[count];
arrayPath=new String[count];
for (int i = 0; i <count; i++) {
imageCursor.moveToPosition(i);
int id = imageCursor.getInt(image_Column_Index);
int dataColumnIndex = imageCursor.getColumnIndex(MediaStore.Images.Media.DATA);
arrayPath[i] = imageCursor.getString(dataColumnIndex);
// APP CRASHED WITH THIS LINE
thumbnails[i] = MediaStore.Images.Thumbnails.getThumbnail(getActivity().getContentResolver(),id,MediaStore.Images.Thumbnails.MICRO_KIND,null);
}
imageCursor.close();
}
我在循环结束后关闭光标,我不确定为什么我会收到此错误,即使我在不再需要后关闭光标。请指导我进行此修复。 在任何情况下我都没有禁用严格模式的选项,所以我需要在不禁用严格模式的情况下解决这个问题。
错误的完整堆栈跟踪。
12-26 10:21:58.358 12925-12925/com.example.testD/Bottom Sheet: Parent = null Context com.elaxer.Navigation_Drawer@cbf3705
12-26 10:21:59.976 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 769
12-26 10:21:59.976 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 771
12-26 10:21:59.976 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 20752
12-26 10:21:59.976 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 20753
12-26 10:21:59.976 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 20754
12-26 10:22:01.059 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 2
12-26 10:22:01.149 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 2
12-26 10:22:01.255 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 2
12-26 10:22:01.334 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 2
12-26 10:22:01.788 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41985
12-26 10:22:01.788 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41986
12-26 10:22:01.788 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41987
12-26 10:22:01.788 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41988
12-26 10:22:01.788 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41990
12-26 10:22:01.789 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41996
12-26 10:22:01.867 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41985
12-26 10:22:01.867 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41986
12-26 10:22:01.867 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41987
12-26 10:22:01.867 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41988
12-26 10:22:01.867 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41990
12-26 10:22:01.867 12925-12925/com.example.testW/ExifInterface: Skip the tag entry since tag number is not defined: 41996
12-26 10:22:01.904 12925-12933/com.example.testE/StrictMode: A resource was acquired at attached stack trace but never released. See java.io.Closeable for information on avoiding resource leaks.
java.lang.Throwable: Explicit termination method 'close' not called
at dalvik.system.CloseGuard.open(CloseGuard.java:180)
at java.io.FileInputStream.<init>(FileInputStream.java:78)
at java.io.FileInputStream.<init>(FileInputStream.java:103)
at android.media.ExifInterface.loadAttributes(ExifInterface.java:1338)
at android.media.ExifInterface.<init>(ExifInterface.java:1057)
at android.media.ThumbnailUtils.createThumbnailFromEXIF(ThumbnailUtils.java:479)
at android.media.ThumbnailUtils.createImageThumbnail(ThumbnailUtils.java:96)
at android.provider.MediaStore$InternalThumbnails.getThumbnail(MediaStore.java:753)
at android.provider.MediaStore$Images$Thumbnails.getThumbnail(MediaStore.java:1085)
at com.elaxer.mainScreenFragments.BottomSheet.getRecentImages(BottomSheet.java:207)
at com.elaxer.mainScreenFragments.BottomSheet.onCreateView(BottomSheet.java:69)
at androidx.fragment.app.Fragment.performCreateView(Fragment.java:2600)
at androidx.fragment.app.FragmentManagerImpl.moveToState(FragmentManagerImpl.java:881)
at androidx.fragment.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManagerImpl.java:1238)
at androidx.fragment.app.FragmentManagerImpl.moveToState(FragmentManagerImpl.java:1303)
at androidx.fragment.app.BackStackRecord.executeOps(BackStackRecord.java:439)
at androidx.fragment.app.FragmentManagerImpl.executeOps(FragmentManagerImpl.java:2079)
at androidx.fragment.app.FragmentManagerImpl.executeOpsTogether(FragmentManagerImpl.java:1869)
at androidx.fragment.app.FragmentManagerImpl.removeRedundantOperationsAndExecute(FragmentManagerImpl.java:1824)
at androidx.fragment.app.FragmentManagerImpl.execPendingActions(FragmentManagerImpl.java:1727)
at androidx.fragment.app.FragmentManagerImpl$2.run(FragmentManagerImpl.java:150)
at android.os.Handler.handleCallback(Handler.java:739)
at android.os.Handler.dispatchMessage(Handler.java:95)
at android.os.Looper.loop(Looper.java:148)
at android.app.ActivityThread.main(ActivityThread.java:5417)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
12-26 10:22:01.906 12925-12933/com.example.testW/System.err: StrictMode VmPolicy violation with POLICY_DEATH; shutting down.
12-26 10:22:01.906 12925-12933/com.example.testI/Process: Sending signal. PID: 12925 SIG: 9
【问题讨论】:
-
如果您正在“获取 uri 的路径”,为什么要使用 stric 模式...从 uri 获取路径太糟糕了,您不必担心严格模式
-
@Selvin 我需要通过启用严格模式来解决这个问题。有什么解决办法吗?
-
这与
MediaStore.Images.Thumbnails.getThumbnail的内部代码有关,因此您无法修复它,但如果没有完整的堆栈跟踪,则很难猜测...只需禁用严格模式 -
@Selvin 完整堆栈跟踪添加
-
@Ritu, 你
recycle使用后的位图是造成泄漏的原因吗?
标签: java android cursor android-strictmode