Open wbarnard opened 6 years ago
Can you please post the code you are using and the stacktrace?
We need to have a more graceful handling of errors.
facing the same issue. App crashes on calling the run method.
last logged lines are:
Videokit: start run in main.
Videokit: term_init & parse options.
I am having the same error also
07-07 22:28:00.213 11191-11191/ I/Videokit: start run in main.
register_exit
07-07 22:28:00.214 11191-11191/ I/Videokit: term_init & parse options.
More Details having same issue
15/com.madhavanmalolan.ffmpegandroidtest I/Videokit: start run in main. 2018-11-15 12:54:17.334 13715-13715/com.madhavanmalolan.ffmpegandroidtest I/Videokit: register_exit 2018-11-15 12:54:17.334 13715-13715/com.madhavanmalolan.ffmpegandroidtest I/Videokit: term_init & parse options. 2018-11-15 12:54:17.385 13715-13715/com.madhavanmalolan.ffmpegandroidtest I/Videokit: finished parse options. 2018-11-15 12:54:17.385 13715-13715/com.madhavanmalolan.ffmpegandroidtest I/Videokit: in transcode(). 2018-11-15 12:54:17.385 13715-13715/com.madhavanmalolan.ffmpegandroidtest I/Videokit: befor transcode_init(). 2018-11-15 12:54:17.435 1297-2382/? W/InputDispatcher: channel 'e5f113f com.madhavanmalolan.ffmpegandroidtest/com.madhavanmalolan.ffmpegandroidtest.MainActivity (server)' ~ Consumer closed input channel or an error occurred. events=0x9 2018-11-15 12:54:17.435 1297-2382/? E/InputDispatcher: channel 'e5f113f com.madhavanmalolan.ffmpegandroidtest/com.madhavanmalolan.ffmpegandroidtest.MainActivity (server)' ~ Channel is unrecoverably broken and will be disposed! 2018-11-15 12:54:17.436 1297-3596/? I/WindowManager: WIN DEATH: Window{e5f113f u0 com.madhavanmalolan.ffmpegandroidtest/com.madhavanmalolan.ffmpegandroidtest.MainActivity}
same issue occur how to resolve this.
I am experiencing a crash when calling Run. I have the same problem when integrating with my own application and with the example project in github. With the example project I only updated the build tools and gradle plug-ins to the latest versions and commented out the bintray section which wasn't building.
The last trace output is "term_init & parse options.". It gets to the same point whatever parameters I send to Run. So it looks like it is falling over during the initialisation.
The same problem occurs on an Armv7 device running Android 5.0.1 and an Armv8 device running Android 7.1.1.
I have tried adding code to give runtime write external strorage permissions which I have confirmed is working.