Battery drain when quicly forward or backward tracks many times

[alickbuscariolli]

Hi team,

I'm experiencing significant battery drain and device overheating issues when using the just_audio package in my Flutter application. Specifically, when I rapidly skip forward and backward through the audio tracks in my playlist, the battery consumption spikes, and the device becomes excessively hot.

To Reproduce
Steps to reproduce the behavior:

Setup Audio Sources:

Utilize ConcatenatingAudioSource with multiple ClippingAudioSource and AudioSource.uri instances.
Example configuration:

final playlist = ConcatenatingAudioSource( children: [ ClippingAudioSource( start: Duration.zero, end: Duration(minutes: 3), child: AudioSource.uri(Uri.parse('https://example.com/audio1.m3u8')), ), ClippingAudioSource( start: Duration.zero, end: Duration(minutes: 4), child: AudioSource.uri(Uri.parse('https://example.com/audio2.m3u8')), ), // Add more audio sources as needed ], );

Initialize Audio Player:

Set the concatenated audio source to the player.

await _audioPlayer.setAudioSource(playlist); await _audioPlayer.play();

Interact with Playback:

Rapidly skip forward and backward through the tracks using playback controls.
For example:

_audioPlayer.seekToNext(); _audioPlayer.seekToPrevious();

Observe Device Behavior:

Notice the rapid battery drain and the device becoming unusually hot during these interactions.
Expected behavior
The audio player should handle rapid navigation through tracks smoothly without causing excessive battery consumption or overheating the device.

Actual behavior
Repeatedly skipping forward and backward through the playlist leads to significant battery drain and the device heating up noticeably.

[github-actions]

Oops, it appears that your issue did not follow the template and is missing one or more required sections. Please open a new issue, and provide all required sections and information.

FAQ:

1. Do I really need to submit a minimal reproduction project for a bug? A: Yes. I prioritise bugs secondarily on how many people are affected, and primarily on whether the bug report is complete, in the sense that it enables me to immediately reproduce it and start working on a fix. If a bug is important to you, the best thing you can do is to provide all requested information ASAP so that I can start looking into it ASAP.

2. I think I supplied all required information, so did the bot make a mistake? A: The bot only checks the section headings, so when you post a new issue, make sure you leave the section headings intact. (Note that because of this, it is even possible to trick the bot by including only the section headings, and then not providing the requested information under each heading. This is frowned upon, and the issue will be closed manually.)

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs, or use StackOverflow if you need help with just_audio.