Comment 4 for bug 840860

For 1.10, I added a simple warning message about this problem when reload track metadata. That should be a good enough band-aid until we can figure out a good way to actually solve the problem.