This happens only for certain jpg image file. After I select the image and choose the save path, and after the app starts to process, it will get stuck at 0% and seems not to be able to finish. I further check the save path, there is a new file, and its size is growing with time (to tens of MB and to hundreds of MB).
I have attached a sample of a jpg file causing the problem and the created image file when this happens. It seems not to relate to exif removing part but the jpg image itself, as I use another remover to remove the exif data and this problem still happens. The sample jpg image I provide here is exif-removed.
Please note that it seems Media Storage (com.android.providers.media.module) cannot correctly handle the created image file in this case, and it will consume CPU at 100% when it tries to work on this file. After remove this file and reboot, Media Storage won't consume CPU any more. (This is how I notice this problem: as my phone is heating up for no reason, I found Media Storage is consuming CPU and from the list of its opened files there is this image file created by Exif-Eraser)
sample.zip
Thank you for this amazing app.
Description
This happens only for certain jpg image file. After I select the image and choose the save path, and after the app starts to process, it will get stuck at 0% and seems not to be able to finish. I further check the save path, there is a new file, and its size is growing with time (to tens of MB and to hundreds of MB).
I have attached a sample of a jpg file causing the problem and the created image file when this happens. It seems not to relate to exif removing part but the jpg image itself, as I use another remover to remove the exif data and this problem still happens. The sample jpg image I provide here is exif-removed. Please note that it seems Media Storage (com.android.providers.media.module) cannot correctly handle the created image file in this case, and it will consume CPU at 100% when it tries to work on this file. After remove this file and reboot, Media Storage won't consume CPU any more. (This is how I notice this problem: as my phone is heating up for no reason, I found Media Storage is consuming CPU and from the list of its opened files there is this image file created by Exif-Eraser) sample.zip
Environment
Thanks in advance!