1014539 - Very slow response time when a lot of elements with listeners

Status: UNCONFIRMED

(Core :: SVG, defect)

Description

[lejav]

I have a lot of SVG elements with listeners on it doing only setTimeout 250 ms and displaying the delay to launch the setTimeout function. I notice abormally long delays. Everything is fine with IE and Google Chrome.
Please, see http://jsfiddle.net/TbKtn/ and click on the black circle.

Comment 1

[lejav]

I forgot to mention that I tried with a fresh installation of firefox, with safe mode and with all plugins disabled.

Comment 2

[Jonathan Watt [:jwatt]]

Can you create a simple standalone test file and attach it using the "Add an attachment" link, please? jsfiddle pulls in a lot of stuff that makes it impractical to analyze.

Comment 3

[lejav]

Attachment: Just run this file in firefox

Comment 4

[Jonathan Watt [:jwatt]]

Thanks. For me using that testcase the setTimeout message is displaying pretty close to 250 ms. I did see it around 1250 ms once, but haven't been able to get that to happen again despite many attempts.

Comment 5

[lejav]

I just tried on another laptop under Windows 7, and exactly problem: very bad values for firefox and always around 250 ms for Chrome.

Comment 6

[Timothy Nikkel (:tnikkel)]

I see 251 ms here as well, on mac.

Comment 7

[lejav]

I could do other tests on other computers (always 29.0.1 and Windows 7).
I noticed that problem appears after some limit on the number of elements; it seems to be related to the memory configuration.
Please, could you try after having increased the loop value in the html file; let's say 30000 instead of 10000, or 50000.

Comment 8

[Timothy Nikkel (:tnikkel)]

What kind of numbers are you getting when the problem happens?

Comment 9

[lejav]

As stated before, I noticed that it depends on the computer configuration (it seems to be related to the memory configuration). For my configuration, with a loop with 10000, I have response times around 400-600 ms. Sometimes more, even more than 1 second. For a friend, with 10000, it was OK, but with 30000 it was around 500 ms (he has 8 GB RAM against 4 GB for me). For both, it is always 250 ms with Chrome, whatever is the loop.

Comment 10

[lejav]

Could you reproduce it?