If loaded more than once, jasmine.Clock.real will no longer contain the real methods, and any call to say setTimeout will call itself and goes into an infinite loop.
This happens in Safari, and maybe IE as well.
(We are using js-test-driver + code coverage, which leads to Jasmine getting loaded twice, we have no control over it...)
The code I have which fixes this is at https://github.com/pivotal/jasmine/pull/249/files , it prabably doesn't handle commonJS correctly as it assumes window to be present
What's the use case for loading Jasmine twice?
It turns out to be a bug of js-test-runner
Ok, closing then. It should probably be fixed on that side.