Good to know - it definitely works best in Safari and Chrome right now (since they have the best-optimized JS implementations). I'm surprised Firefox is hanging that badly but I'll look into it.
The problem is actually, more or less, building up the search index - this is only an issue the first time you do a particular kind of search, and it's fast after that. This involves parsing all the source code, which is a recursive process, which FF doesn't optimize (whereas Safari and Chrome zip through it much faster).