Firefox 27 SunSpider

[#1]

Has anyone else noticed problems with Firefox when running SunSpider 1.0.2?
http://www.webkit.org/perf/sunspider-1.0.2/sunspider-1.0.2/driver.html
After the benchmark completes, the browser seems to just completely die. It never displays the results page, and attempts to load other sites in a new tab result in it spinning circles until the browser is closed and re-opened.
I'm sure it must be me - something like this would surely be picked up by the developers before release.

[#2]

Seems ok here.
RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                126.6ms +/- 3.1%
--------------------------------------------
  3d:                  21.9ms +/- 7.0%
    cube:                7.7ms +/- 8.8%
    morph:              4.6ms +/- 8.0%
    raytrace:            9.6ms +/- 10.0%
  access:              10.6ms +/- 8.5%
    binary-trees:        1.6ms +/- 23.1%
    fannkuch:            4.6ms +/- 8.0%
    nbody:              2.1ms +/- 10.8%
    nsieve:              2.3ms +/- 15.0%
  bitops:                7.0ms +/- 14.4%
    3bit-bits-in-byte:  0.7ms +/- 49.3%
    bits-in-byte:        1.8ms +/- 16.7%
    bitwise-and:        1.8ms +/- 16.7%
    nsieve-bits:        2.7ms +/- 12.8%
  controlflow:          1.7ms +/- 20.3%
    recursive:          1.7ms +/- 20.3%
  crypto:              10.3ms +/- 4.7%
    aes:                5.0ms +/- 0.0%
    md5:                3.1ms +/- 7.3%
    sha1:                2.2ms +/- 13.7%
  date:                15.9ms +/- 7.5%
    format-tofte:        7.1ms +/- 3.2%
    format-xparb:        8.8ms +/- 13.7%
  math:                11.9ms +/- 5.3%
    cordic:              2.0ms +/- 0.0%
    partial-sums:        8.3ms +/- 4.2%
    spectral-norm:      1.6ms +/- 23.1%
  regexp:                8.6ms +/- 4.3%
    dna:                8.6ms +/- 4.3%
  string:              38.7ms +/- 1.2%
    base64:              4.1ms +/- 5.5%
    fasta:              5.0ms +/- 0.0%
    tagcloud:          10.3ms +/- 3.4%
    unpack-code:        14.5ms +/- 2.6%
    validate-input:      4.8ms +/- 6.3%

[#3]

Which version of F/F are you using to test with
I am using 26.0
Here are my results
[code=SunSpider test file=Results]Content Version: sunspider-1.0.2
Run Again

(You can bookmark this results URL for later comparison.)
To compare to another run, paste a saved result URL in the text field below and press enter:

============================================
RESULTS (means and 95% confidence intervals)
--------------------------------------------
Total:                  492.7ms +/- 11.6%
--------------------------------------------
  3d:                    82.6ms +/- 5.7%
    cube:                31.9ms +/- 6.6%
    morph:              13.7ms +/- 3.5%
    raytrace:            37.0ms +/- 7.8%
  access:                43.6ms +/- 6.0%
    binary-trees:        6.7ms +/- 36.3%
    fannkuch:            14.9ms +/- 7.3%
    nbody:              10.0ms +/- 4.8%
    nsieve:              12.0ms +/- 12.2%
  bitops:                20.1ms +/- 3.9%
    3bit-bits-in-byte:    2.1ms +/- 10.8%
    bits-in-byte:        6.3ms +/- 5.5%
    bitwise-and:          3.9ms +/- 5.8%
    nsieve-bits:          7.8ms +/- 3.9%
  controlflow:            4.6ms +/- 10.9%
    recursive:            4.6ms +/- 10.9%
  crypto:                39.6ms +/- 7.2%
    aes:                20.7ms +/- 10.4%
    md5:                10.9ms +/- 9.0%
    sha1:                8.0ms +/- 4.2%
  date:                  68.5ms +/- 13.7%
    format-tofte:        36.4ms +/- 19.2%
    format-xparb:        32.1ms +/- 13.5%
  math:                  39.3ms +/- 2.6%
    cordic:              7.0ms +/- 4.8%
    partial-sums:        27.3ms +/- 3.9%
    spectral-norm:        5.0ms +/- 0.0%
  regexp:                29.4ms +/- 3.7%
    dna:                29.4ms +/- 3.7%
  string:              165.0ms +/- 34.8%
    base64:              15.6ms +/- 9.5%
    fasta:              17.0ms +/- 11.0%
    tagcloud:            37.9ms +/- 5.6%
    unpack-code:        76.9ms +/- 70.6%
    validate-input:      17.6ms +/- 9.0%[/code]

[#4]

It was 27.0. I gave up after several attempts resulted in the same behaviour. Mozilla's Kraken benchmark exhibited the same behaviour.
I just tried on my home PC, also running FF 27.0 and there are no problems, so it would appear it's some configuration issue with my work PC (out of my hands).

[#5]

Perhaps you can mention your findings to your works I.T Department ??