media icon indicating copy to clipboard operation
media copied to clipboard

H.265 (HEVC) + widewine some devices reboots

Open CrashBashMD opened this issue 1 year ago • 4 comments

Version

Media3 1.1.1 / ExoPlayer 2.19.1

More version details

Hi, I got problem with some of h.265 streams with widevine. One of tested device reboots (another is returning decoding error - separate issue). At the moment I cannot share the stream, however I'm working on it. We also had tested on newest media3 1.4.1 but results were the same. I attach logs, maybe there is something you will see. restart_galaxy_tab.log

My apologies for no stream or reproduction steps. I'm working on it.

Devices that reproduce the issue

Samsung Galaxy Tab A8 running on android 11

Devices that do not reproduce the issue

Samsung Galaxy S20 FE on android 13

Reproducible in the demo app?

Not tested

Reproduction steps

Currently only logs available. Working on repro app

Expected result

No device reboot

Actual result

Device reboots after initializing the stream. Looks like DRM related issue

Media

H.265 stream with widevine L1

Bug Report

  • [x] You will email the zip file produced by adb bugreport to [email protected] after filing this issue.

CrashBashMD avatar Sep 23 '24 14:09 CrashBashMD

Please email us the result of adb bugreport (and update this issue) once you have a local repro and we can take a look.

icbaker avatar Sep 23 '24 15:09 icbaker

Bugreport has been sent

CrashBashMD avatar Sep 26 '24 11:09 CrashBashMD

The logcat unfortunately did not capture the reboot cause and he bugreport did not capture the logs of playback or tombstones for the reboot cause. Can you share another bugreport, please?

rrfrias avatar Oct 03 '24 04:10 rrfrias

another bugreport sent

CrashBashMD avatar Oct 21 '24 09:10 CrashBashMD

Is it possible to send me a true bugreport. 401886_bugreportsTablet.txt.zip contains a logcat 401886_bugreportsTablet.txt but none of the other files usually collected in a bugreport including tombstones.

Either run adb bugreport after the device reboots or follow these instructions https://developer.android.com/studio/debug/bug-report?

Was phonelogcat.txt the logcat before the crash occurred?

Also, can you grant permission to share these logs with Samsung?

rrfrias avatar Oct 31 '24 01:10 rrfrias

Hey @TeaFather. We need more information to resolve this issue but there hasn't been an update in 14 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

google-oss-bot avatar Nov 19 '24 02:11 google-oss-bot

additional bug reports were send on 5th November.

CrashBashMD avatar Nov 19 '24 08:11 CrashBashMD

Sorry for the delay in investigating this issue. I looked at both the bugreports

  • bugreport-gta8xx-UP1A.231005.007-2024-10-31-10-14-29.zip
    • There is a tombstone but it seems to occur at startup and is unrelated to media playback functionality.
    • In the logcat there is a java.lang.IllegalArgumentException but it does not seem to be in the playback path. Later a number of services were killed but i cannot tell what precipitated that event.
  • bugreport-a14xmue-UP1A.231005.007-2024-10-31-11-14-13.zip
    • There are two tombstones. Those seem to be in the audio path.
    • I don't see related/significant errors in the log

Do you know if these bugreports were captured after the playback failure or during? If after, we would like your permission to share the second bugreport with MediaTek+Samsung as the tombstones indicate that the crash happened in the audio codec.

If you can provide repro steps that would also help MediaTek/Samsung reproduce.

rrfrias avatar Jan 21 '25 20:01 rrfrias

Thanks for investigating,

Sure, please share with MediaTek. Steps were just to try play certain h.265 stream with widevine on some samsung devices

CrashBashMD avatar Jan 27 '25 13:01 CrashBashMD

Are you seeing this with the Exoplayer demo app? Can you mention the test clip that it failed with, device names and version. I can check but they might not be pushing updates to Samsung Galaxy Tab A8 running on android 11 and might not choose to investigate issues on this device. Repro steps and device information will be very helpful.

I have shared bugreport-a14xmue-UP1A.231005.007-2024-10-31-11-14-13.zip with MediaTek in internal tracker 394422890

rrfrias avatar Feb 05 '25 01:02 rrfrias

Here what I got reported: _On the Samsung phone: Under Clear DASH, the UHD (MP4, H265), UHD (WebM, VP9) videos could not be played. Under Widevine DASH (MP4, H265), the UHD (cenc) video could not be played. The messages were Unable to initiate decoder

on the samsung Tablet: Under Clear DASH, the UHD (MP4, H265) could not be played with message playback failed Under Widevine DASH (MP4, H265), the UHD (cenc) video could not be played with message Unable to initiate decoder_

I didn't received logs from those

Image Image

CrashBashMD avatar Feb 21 '25 08:02 CrashBashMD

Hey @TeaFather. We need more information to resolve this issue but there hasn't been an update in 14 weekdays. I'm marking the issue as stale and if there are no new updates in the next 7 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

google-oss-bot avatar Mar 13 '25 01:03 google-oss-bot

Since there haven't been any recent updates here, I am going to close this issue.

@TeaFather if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

google-oss-bot avatar Mar 24 '25 01:03 google-oss-bot