I'm seeing the same issue in the same exact place (starting in 5.3.2) but for me, there are 2 ids that give 3 results (2 of which are identical, due to a left outer join).

I took a look at the proposed fix and don't believe it addresses that scenario.