Skip to content

SVGResize test takes too long to stabilize in Firefox. #53

Open
jdalton opened this Issue Sep 24, 2012 · 7 comments

4 participants

@jdalton
jdalton commented Sep 24, 2012

I haven't had the chance to dig into the code, but something is causing the SVG resize test to take ~15 minutes or more to finish, which is waaaaaaaaaay to long.

Is there something in the code that waits for it to stabilize or smth that would cause the test to take so long to finish?

@nateridderman

I also noticed the delay in Firefox. I let it run at least 10 minutes and then gave up.

@nateridderman

Actually happened to me in Chrome too. I'm running Windows 7 64-bit.

@jkomoros
jkomoros commented Nov 6, 2012

I've noticed this problem a number of times, too. My assumption was always that the main test function could take a variable amount of time (despite being the same basic operation) and that benchmark.js was waiting for the results to stabilize, which would take a long time.

But jdalton, it sounds like this is not expected behavior of benchmark.js. Do you have any other ideas about what could be going on?

@jdalton
jdalton commented Nov 7, 2012

But jdalton, it sounds like this is not expected behavior of benchmark.js. Do you have any other ideas about what could be going on?

Right, Benchmark.js doesn't wait to stabilize so I'm not sure what could be causing the test to wait so long to finish.

@paulirish
robohornet member

Spent some time digging into this, but lost between benchmark's iteration logic and the async test setup.

I'm not sure how to better evaluate the exit conditions that benchmark should be hitting. @jdalton where should I be looking?

@paulirish
robohornet member

I was thinking we should remove SVGResize due to its instability for now. We can revisit as we identify how it can stabilize in benchmark quicker.

Having it out will let us complete the suite successfully on a number of browsers..

@paulirish
robohornet member

SVG resize test commented out for now: 3e5b4fc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.