Hey CrimsonHawk,
Thanks for your report. I have been able to reproduce this behavior, and have tested it and acknowledged that it happens with several nodes.
However, there has been a bug entered for a similar issue with the same root cause that the developers have decided not to fix at this time due to the fact that it does not affect functionality, and that they are currently focusing their efforts on high-priority crash and showstopper bugs.
Have a great day