PlexAmp Bugs (iOS, Linux, etc.)

I’ve been running into a handful of issues with Plexamp lately and wanted to report the information I have on them.

On Linux, the Electron renderer process seems to be crashing arbitrarily; sometimes it takes hours, and other times it happens within the first few minutes of opening the application. There seems to already be a post tracking this issue here.

Additionally, I’ve encountered a (somewhat) set of issues that occur when skipping tracks; both of which I’ve been able to reproduce on both iOS and Linux.

The first of these essentially results in two tracks or more being played simultaneously, where the player controls (e.g. pausing) will affect both tracks. In some cases, the combined audio of both tracks becomes cached in such a way that selecting a different track, then switching back to the first track doesn’t seem to resolve the issue… In one instance I’m fairly certain I had this issue persist through app restarts, but wasn’t able to resolve it until I cleared the cache manually.

The second issue occurs when skipping tracks and it essentially soft-locks the application. The app appears to get stuck loading (or possibly transitioning to/from) a given track, where there’s a spinner over the Play/Pause button, however the track never loads and the application simply hangs.

On iOS, the app is still navigable (sort of), and various UI elements will still respond but not necessarily function correctly. For example, the track play/pause/seek/timeline controls stop functioning, but the user is still able to view the “Up Next” queue or navigate back to the home screen of the app; attempting to play a different track, however, will have no effect. The system media controls also seem to fail to communicate with Plexamp as well

On Linux, the entire application stops responding to any and all user input (with the exception of scrolling), and appears to the entire DOM updating logic to lock up. The spinner over the Play/Pause button remains active, and will continue spinning, but resizing the window will no longer trigger any type of resizing logic and will instead result in additional window space being filled in with gray (see the screenshot below).

In my efforts to debug this I noticed that, in some cases, Electron’s embedded dev tools will stop responding (sometimes completely disconnect) - and I also managed to cause my Plex Server instance to enter some sort of unresponsive state… twice (although I did manage to pull logs for the first time).

Both of the issues above tend to occur under similar circumstances, but don’t reliably occur under the same circumstances. The steps I’ve been using to reproduce them are:

  1. Open Plexamp
  2. Play the “Fresh :heart:” playlist
  3. Repeatedly hit the “next track” button in rapid succession until the issue occurs
    The amount of skips required before soft-locking can vary greatly; I’ve had it happen within the first 10 skips (not even in rapid succession), and in other cases it’s taken dozens of skips. It’s also worth noting that in some cases both issues will occur at the same time (I’ve confirmed this on iOS). I’ve also noticed that the soft-lock tends to occur less frequently when playing a lot of tracks in their “natural” order (e.g. from “Tracks” or from within their native album with shuffle turned off); since automatically generated playlists and mixes tend to have far more inconsistency in their ordering, I’ve been using those to test.

Update:

The soft-lock issue happens on Android as well.

1 Like

Does the soft lock only happen when interacting with the Plexamp UI or via external player controls as well?

Both, I just confirmed that it still occurs using the player controls in the iOS Control Center, and I’m fairly certain that several of my earlier experiences with this issue were via Bluetooth controls while driving.

And just to be pedantic, is this just next-ing through a playlist, or is there AutoPlay involved as well?

I’m not entirely sure.

I’ll create a large playlist consisting of very short tracks (< 10 sec) and test that when I get the chance.

I know, for a fact, that it happens specifically when skipping to the next track, but I’m not completely certain what the situation was while I was driving since I couldn’t check my phone. In that particular case though, I believe it may have gotten stuck when I skipped to the next track but continued to play audio until the track finished; since the app was soft-locked internally, it never continued on to the next track after the “current” one was completed.

It’s also probably worth pointing out that I’ve been able to trigger the soft lock while skipping through tracks in “album” mode without shuffle on.

what is “album” mode?

sorry to be pedantic, but details matter since i haven’t been able to reproduce.

No problem. I suppose I was referring to what was in the play queue at the time (vs shuffling an arbitrary playlist or the whole library); I started on track 2 of one album (which has 10 tracks total) and hit “next” several times so that it tried to play the first track of the next album by the same artist, and the soft-lock occurred on track 1 of that next album.

In the original post I had mentioned that most of my tests were happening when I was the queue was in no particular order (often a shuffled playlist, or radio), and I just wanted to point out that the issue does still happen when playing albums in order, etc.

I haven’t been able to get this issue to happen with downloaded content (yet).

I do have video for the whole process for both iOS and desktop if that helps.

Linux: Plexamp 3.8.2 Linux Soft-Lock - YouTube (Screen tearing unrelated)

Update: I just tried this against someone else’s server and was unable to reproduce the issue. I then went back and tried against a second library on my own server and was able to reproduce the issue again, so it would seem that something is up with my own Plex instance. I’m not really sure what would be the issue, though, since I’m running the latest stable Docker image (1.25.1.5286) and am usually connecting via LAN.

it really shouldn’t relate to your server unless it’s somehow related to auto play, which is why i was asking about it earlier.

I haven’t been able to reproduce the behavior on downloaded tracks either, which leads me to believe that there’s something weird happening either with the network requests or on the server side.

For what it’s worth, I’ve definitely caused some kind of issue on the server-side a handful of times while messing with this issue; usually the Plex server itself will stop responding to the point where even trying to access it via https://app.plex.tv fails. When I checked the docker container it seemed that all the required processes were running, but I generally end up restarting the container after a few minutes of waiting and download the logs after I’m able to access it again.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.