_Comment made by: favila_
Update in CLJS-847: original reporter was not able to reproduce his original bug report in Safari 6.0.x running in BrowserStack. This may be because of BrowserStack, but it's the best we have.
Given how hard this bug is to reproduce, how few people it affects, and how significant the performance regression is, I still think we should go back to the simple {{(if (nil? x) "" (.toString x))}} implementation. However, you could also try the patch on this ticket (using a typeof switch), which at least (_handwaving_) *might* fix this bug in Safari 6.0.x and is a little faster than a simple .toString in Chrome and not much slower elsewhere. (The reason I think it might avoid this bug in Safari is that it avoids calling .toString on non-Objects.)