Hello,
sometimes I start up the application to resume playback only to find my last played queue being overwritten with another queue’s tracks but different position. The queue’s name is unaffected, only the content is corrupted.
How to fix it?
Upload description: Another - queue corruption
Subsonic
Please make some efforts when posting, there’s not enough information to understand your issue here.
Sorry, I don’t know how else to explain it but I will try an example 
I have an album A and a playlist P.
First, I play A, this opens a media queue with all tracks from A that is also named “A". Then in the middle of playback of that queue A I will start playing P, which creates a new queue “P” with all the tracks from the playlist.
Then I stop listening at some point. Both queues now have their states saved, which song I last listened to in each queue respectively.
The next day, I want to continue listening to queue P, but upon opening the application, I find that both queues A and P now contain all tracks from Album A and no tracks from playlist P, although queue P is still named “P". This is the corruption I am experiencing.
I have no reproduction steps, it just happens on some days and not on others. The logs are from a timeframe that this happened in.
Specifically it seems that the last queue is overwritten with the contents of the first in the list.
In those logs there’s never a save of the queue, if you reload the other queue then open it again does it have the proper content ?
And what is the queue size of Exp 33 and the one of wicked ?
No, if I go back to exp33 and then back to wicked, the tracks in wicked stay exp33. Both queues have 170 tracks, which is the size of the exp33 playlist! But the wicked queue playback is at position 15 (no random, no repeat), exp33 is at 32 (random and repeat). But they appear to have the same order of songs.
Can you provide logs loading exp33 then another then wicked then exp33 then create a new queue then load wicked.
The new log is called “Another - queue corruption 2”
Does not seems to be present on the server.
Tried again:
Another - corrupted queue
Ok so the logs works as expected. Means the previous logs did not capture the actual moment of the corruption 
I guess you’ll need to keep logs enabled until you reproduce again.
