material-components / material-components/material-components-android

[MaterialContainerTransform] Shared element transition with PlayerView (Exoplayer2)

Open
#1,249 6 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug Feature: Transition
Dominant language
Java
Stars
17.4k
Forks
3.2k
PR merge metrics
No merged PRs in 30d

Description

**Description:**
Using the latested library with a shared element transition containing in Fragment B a VideoView from Excoplayer crashes sometimes. No Exception is shown in Logcat just always the Signal11, as described later. If I set View as GONE transition works and never crashes, if VideoView is visible (doesn't matter if playing or paused) it crashes sometimes.

**Expected behavior:**
Here is a video where it works sometimes and then crashes.
https://we.tl/t-JYL6i18VF7

**Source code:**
Using Arch Navigation to switch between fragments.

**Android API version:** 29

**Material Library version:** com.google.android.material:material:1.2.0-alpha06
com.google.android.exoplayer:exoplayer:2.11.0

**Device:** Tested on Emulator and Pixel 4

A/RefBase: decStrong() called on 0xbd102580 too many times
--------- beginning of crash
1587902454.929 A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x4 in tid 15702 (hwuiTask1), pid 15510 (com.megalol.app)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the crash in the MaterialContainerTransform shared-element transition between Fragment B and the Exoplayer2 PlayerView, using Android API 29 and the listed library versions. Compare the transition with the PlayerView visible and set to GONE; done means the visible view no longer intermittently produces the reported SIGSEGV.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.