Side navigation
#2846 closed bug (wontfix)
Opened May 12, 2008 05:20PM UTC
Closed July 28, 2010 02:51AM UTC
Last modified March 09, 2012 02:57PM UTC
FF2 infinite loop in jQuery animation onComplete
| Reported by: | zbuffered | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.2.4 |
| Component: | effects | Version: | 1.2.1 |
| Keywords: | animation, onComplete, infinite loop | Cc: | |
| Blocked by: | Blocking: |
Description
I clicked on a link I had built with jQuery, only to find that my CPU utilization pegged out and the link did not work. I had a difficult time replicating this issue and I think I have enough to submit a bug report on.
The link uses jQuery to animate a container open and closed. When it opens or closes the container, the height of the page changes, and I have to run another function to resize other elements on the page to fit. I set this up in a non-ideal way, and as a result, some configurations on our site don't have the function defined. I have solved this but it uncovered a pretty nasty little bug that doesn't appear to exist with IE6 or IE7 or FF3b5.
Description: the onComplete event runs when the animation is complete. If it references a function that doesn't exist, Firefox 2 repeatedly runs the oncomplete code in an infinite loop, whereas other browsers fail gracefully.
I stripped it down to a decent example, sorry I have not had a chance to look through jQuery to see what is specifically going on.
Attachments (1)
Change History (4)
Changed May 12, 2008 07:48PM UTC by comment:1
Changed May 12, 2008 09:10PM UTC by comment:2
Also, the link appears to crash FF3b5 about every third time it is loaded and run.
A lot of things crash FF3 right now though, so I'm not too concerned
Changed May 20, 2008 07:42PM UTC by comment:3
Priority is probably not 'major', sorry this was my first bug report :)
Changed July 28, 2010 02:51AM UTC by comment:4
| resolution: | → wontfix |
|---|---|
| status: | new → closed |
FF2 is no longer supported; if this bug still exists and someone has a patch against 1.4.2, feel free to reopen the ticket.
I suppose it never reaches the clearInterval as it errors while stepping.
Maybe we could wrap line 384:
With a try/catch.