Uninlining js::Vector<T,N,AP>::calculateNewCapacity() makes the problem go away, but how come we've only started seeing this issue in Firefox 10? :(
Uninlining js::Vector< T,N,AP> ::calculateNewC apacity( ) makes the problem go away, but how come we've only started seeing this issue in Firefox 10? :(