I just had this problem and was able to fix it by adding a meta tag with the utf-8 encoding to the head section of the page I was developing
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
It's the result of a couple of bugs. The reason the above fixes it: Tincr loads files from the filesystem using utf-8 encoding but depending on your platform and/or web server, Chrome won't always load content using utf-8 unless you tell it to. If you have non-latin characters in your source. The content in your browser doesn't match the content on the file system so Tincr keeps trying to reload it. It shouldn't do that but while I work on fixing that, you can use the above work around.