This doesn't exactly seem like a bug, just messy behaviour from the music client IMO. Since I don'y know the particulars of how the player works, I'll try and explain the best I can. I'm not sure if you have noticed this, but when you choose "play now" on a single song, it plays it, but puts the whole album on the current playlist. Also, the "play next" seems to mess the playlist a bit.
From what I can gather, the "now playing" and the playlist itself aren't necessarily related, since I can have a totally empty "current playlist" while having a "now playing song" active. As a result of having two pools of files to draw from, the player tends to mess things up a bit by either not playing what's on the playlist or not allowing the user to manipulate it. In more extreme cases, this conflict ends up in app crash.
Sorry to be so vague, but I can give examples if necessary, although I think this behaviour is self evident with a bit of manipulation in the music app
From what I can gather, the "now playing" and the playlist itself aren't necessarily related, since I can have a totally empty "current playlist" while having a "now playing song" active. As a result of having two pools of files to draw from, the player tends to mess things up a bit by either not playing what's on the playlist or not allowing the user to manipulate it. In more extreme cases, this conflict ends up in app crash.
Sorry to be so vague, but I can give examples if necessary, although I think this behaviour is self evident with a bit of manipulation in the music app