@jacksonp we started seeing that and NS told us it was a bug in Chrome there is a resolution but it's a bit "ugh" I'll dig out what they said to do