[bendilts]

Interestingly, the part that crashed Firefox was one of the simpler tests--typing a bunch of text content in, then resizing and rotating the shapes that contain that text. Firefox didn't give any details as to why it crashed.

The only thing I could even measure that would lead to a crash is memory usage. I just re-ran the test and watched the process's memory usage. It hovered in the 300-400MB range during the first third of the test. Then, during the test I describe, memory usage rocketed to around 1GB, at which point the browser crashed hard.

I'm not sure why Firefox would exhibit this behavior when other browsers don't, but we know a few people at Mozilla (they're customers of ours) so we'll probably reach out.

[carlosreyes]

Why not remove the part of the test that crashed it and post results of the rest of the benchmarks? Those are 3 tests out of 16, I would still like to see how it compares in the other benchmark tests.

Seeing "We're sorry. Firefox had a problem and crashed." as well as its exclusion from the performance summary made it feel like there was a bit of a bias against Firefox, where even in your conclusion it's stated that it performs "quite well" - that sentence does not reflect on the rest of the article at all.

[ck2]

resizing and rotating the shapes that contain that text

Maybe it was hardware acceleration in the particular machine with the particular video driver you use?

Can you try the test on an entirely different video setup just to prove it can get through, even if the numbers cannot be compared?