Hey, thanks for sharing this – the follow-up was really helpful! Did you end up finding a fix or workaround? We’re seeing a possibly related issue when repeatedly reordering only upcoming tracks, without moving anything across the current entry. It works at first, but RemotePlayerService’s memory keeps growing. In a standalone four-song test, we reused existing Queue.Entry values, swapped upcoming entries, and assigned queue.entries back. Memory went from around 14.5 MiB to 22 MiB after 24 reorders and 80 MiB after 350, followed by a memory-limit termination. Have you tried repeating the successful ADBC-style reorder for a while? Curious whether you’ve seen the same memory growth.