Skip to content

MP4 Parser issue after update to 2.18.0 #10381

Closed

Description

@Tolriq

ExoPlayer Version

2.18.0

Devices that reproduce the issue

All

Devices that do not reproduce the issue

No response

Reproducible in the demo app?

Not tested

Reproduction steps

Play the media that I'll send by mail after;

Expected result

IT plays on 2.17.1 and previous versions

Actual result

Parser error:

playerFailed [eventTime=9.03, mediaPos=0.00, window=0, period=0, errorCode=ERROR_CODE_IO_UNSPECIFIED
  com.google.android.exoplayer2.ExoPlaybackException: Source error
	  at com.google.android.exoplayer2.ExoPlayerImplInternal.handleIoException(ExoPlayerImplInternal.java:632)
	  at com.google.android.exoplayer2.ExoPlayerImplInternal.handleMessage(ExoPlayerImplInternal.java:608)
	  at android.os.Handler.dispatchMessage(Handler.java:102)
	  at android.os.Looper.loopOnce(Looper.java:201)
	  at android.os.Looper.loop(Looper.java:288)
	  at android.os.HandlerThread.run(HandlerThread.java:67)
  Caused by: com.google.android.exoplayer2.upstream.Loader$UnexpectedLoaderException: Unexpected IllegalStateException: Top bit not zero: -44491104
	  at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:433)
	  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	  at java.lang.Thread.run(Thread.java:920)
  Caused by: java.lang.IllegalStateException: Top bit not zero: -44491104
	  at com.google.android.exoplayer2.util.ParsableByteArray.readUnsignedIntToInt(ParsableByteArray.java:371)
	  at com.google.android.exoplayer2.extractor.mp4.AtomParsers.parseEsdsFromParent(AtomParsers.java:1686)
	  at com.google.android.exoplayer2.extractor.mp4.AtomParsers.parseAudioSampleEntry(AtomParsers.java:1516)
	  at com.google.android.exoplayer2.extractor.mp4.AtomParsers.parseStsd(AtomParsers.java:987)
	  at com.google.android.exoplayer2.extractor.mp4.AtomParsers.parseTrak(AtomParsers.java:311)
	  at com.google.android.exoplayer2.extractor.mp4.AtomParsers.parseTraks(AtomParsers.java:132)
	  at com.google.android.exoplayer2.extractor.mp4.Mp4Extractor.processMoovAtom(Mp4Extractor.java:515)
	  at com.google.android.exoplayer2.extractor.mp4.Mp4Extractor.processAtomEnded(Mp4Extractor.java:474)
	  at com.google.android.exoplayer2.extractor.mp4.Mp4Extractor.readAtomPayload(Mp4Extractor.java:456)
	  at com.google.android.exoplayer2.extractor.mp4.Mp4Extractor.read(Mp4Extractor.java:254)
	  at com.google.android.exoplayer2.source.BundledExtractorsAdapter.read(BundledExtractorsAdapter.java:127)
	  at com.google.android.exoplayer2.source.ProgressiveMediaPeriod$ExtractingLoadable.load(ProgressiveMediaPeriod.java:1042)
	  at com.google.android.exoplayer2.upstream.Loader$LoadTask.run(Loader.java:412)
	  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) 
	  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) 
	  at java.lang.Thread.run(Thread.java:920) 
]

Media

Will send by mail

Bug Report

Activity

  1. self-assigned this
    on Jun 28, 2022
  2. Tolriq commented on Jun 30, 2022

    @Tolriq
    ContributorAuthor

    Did you get the file?

  3. rohitjoins commented on Jun 30, 2022

    @rohitjoins
    Contributor

    Cannot access the file as it needs access to Google drive.

  4. Tolriq commented on Jun 30, 2022

    @Tolriq
    ContributorAuthor

    @rohitjoins I think I've fixed the perms to allow anyone. Else I'll put the file elsewhere.

  5. rohitjoins commented on Jun 30, 2022

    @rohitjoins
    Contributor

    Was able to access the file and reproduce the issue on the demo app version 2.18.0. We're looking into this.

  6. rohitjoins commented on Jul 7, 2022

    @rohitjoins
    Contributor

    A fix for this bug has been released in the dev-v2 branch.

  7. Tolriq commented on Jul 7, 2022

    @Tolriq
    ContributorAuthor

    @rohitjoins thanks. Do you have an eta for next release? I'm in beta with current version and just need to know if I should revert or wait for fix before release. No need for precise date.

  8. rohitjoins commented on Jul 22, 2022

    @rohitjoins
    Contributor

    @Tolriq release is done with the fix.

  9. locked and limited conversation to collaborators on Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions