Comments by wesealbe (Top 1 by date)

That link shows that the bug was closed as being not being reproducible.

I have had this problem in visual studio 2015 and 2017 as well. I haven't come across a solution to this problem that works for me yet.