I agree with your assessment, I did not see that bug again since I guess 6.6 so I also believe it was indeed fixed in the upstream in the meantime.