-
-
Notifications
You must be signed in to change notification settings - Fork 790
[iOS] arm64 devices crash on ff_hscale_8_to_15_neon function with EXC_BAD_ACCESS #328
Comments
This issue is fixed using the previous version of |
does this problem apply to Android at all? |
I'm not sure. Unfortunately, I couldn't test it. I don't have a working |
Have you got a test case to prove it? I have some arm64 here to run such test. Also, the device is rather old, so if it works there, it will also work on more advanced devices. |
Yes, I do. It is pretty easy actually. On iOS, it is possible to reproduce it using the test-application. If I test "mp4" encoding under the "Video" tab, library crashes with EXC_BAD_ACCESS. I think the same scenario can be tested using the Android test app. Both Android/iOS applications use the same commands for encoding. So if the same bug is there, it will crash there too. It'd be great if you can test this. |
I tested it on my Android arm64 device (BV-6000) and it a) works correctly, and b) I proved that this So, I propose to mark this patch iOS only. After all, the claim on https://git.ffmpeg.org/gitweb/ffmpeg.git/commit/bd831912712e32b8e78d409bfa7ea7e668ce4b42 is that this gives 25% improvement, which is not something one can dismiss lightheartedly. |
Thanks for testing this case. Yes, we can mark this patch iOS only. I will update |
also, avoid patching the src tree for issue tanersener#328
FFmpeg
operations fail with EXC_BAD_ACCESS onff_hscale_8_to_15_neon
function.All iOS devices with arm64 architecture (probably arm64e as well), running
v4.3.1
andv4.3.1.LTS
releases, are affected from this.The crash is caused by ffmpeg commit bd831912712e32b8e78d409bfa7ea7e668ce4b42.
The text was updated successfully, but these errors were encountered: