GNOME Bugzilla – Bug 708015
androidmedia: "Failed to call Java method"
Last modified: 2014-09-01 06:38:52 UTC
Happens on many devices apparently, like the new Nexus 7 (2013 version): 09-13 16:50:19.434: E/GStreamer+amc(25695): 0:00:04.957153320 0x75a26e00 gstamc.c:702:gst_amc_codec_dequeue_output_buffer Failed to call Java method Should add (as a first step) something that prints the Java exception including backtrace and everything whenever a method call fails or we get an exception elsewhere.
From the gst-android mailing list: Here is what I got: gst_amc_codec_dequeue_output_buffer Failed to call Java method java.lang.IllegalStateException at android.media.MediaCodec.dequeueOutputBuffer(Native Method) at dalvik.system.NativeStart.run(Native Method) gst_amc_codec_dequeue_input_buffer Failed to call Java method java.lang.IllegalStateException at android.media.MediaCodec.dequeueInputBuffer(Native Method) at dalvik.system.NativeStart.run(Native Method) Not very useful :(
Does not seem to cause bigger problems though, downgrading importance
commit aee9d12b863ca3faa266b611e70b1bbeaeebb010 Author: Sebastian Dröge <sebastian@centricular.com> Date: Thu Jun 19 11:26:41 2014 +0200 androidmedia: Also don't report warnings for queue/dequeue errors during flushing in error cases ... and fix a case where we released an invalid buffer index. commit 880f3d8a185f0b126ebc2b0ad0b0c12969683053 Author: Sebastian Dröge <sebastian@centricular.com> Date: Thu Jun 19 11:15:56 2014 +0200 androidmedia: Don't consider input buffer queueing failures as an error during flushing commit 71c0e0e19feea20d7262d50438952b2ceef3c544 Author: Sebastian Dröge <sebastian@centricular.com> Date: Thu Jun 19 11:12:47 2014 +0200 androidmedia: Clean up flushing code and don't consider output buffer releasing failures during flushing as an error