Skip to main content

Bug Tracker

Side navigation

#8974 closed bug (invalid)

Opened April 26, 2011 04:43AM UTC

Closed April 26, 2011 05:18AM UTC

Warning : Unresponsive script

Reported by: vishnuprem Owned by:
Priority: undecided Milestone:
Component: misc Version: 1.4.2
Keywords: Cc:
Blocked by: Blocking:

I am encountering a jquery-script error. The error message is

"Warning : Unresponsive script

A script on this page may be busy, or it may have stopped responding. You can stop the script now, open the script in the debugger. or let the script continue."

FYI - The test case is as follows :

I have a html page, in which there is a table of above 1000 rows. The warning shows when this page is loaded. And I have encounterd this Firefox 3.6.10.

Please suggest a solution to avoid this warning.

Attachments (0)
Change History (1)

Changed April 26, 2011 05:18AM UTC by addyosmani comment:1

component: unfiledmisc
resolution: → invalid
status: newclosed

Thanks for submitting a ticket to the jQuery Project. The warning message that you're seeing is generally triggered when Firefox thinks that a script may be running out of control and would make Firefox hang if nothing is done to prevent this behavior.

When you say you have a table of above 1000 rows, it's possible that you're either not using the most efficient jQuery selectors to work with the table, you're attempting to change the style information for the entire data-set, or that the table rows contain a rather large quantity of data themselves, meaning more time and memory may be needed to say, copy a selection of rows.

If for example you have a table with thousands of rows that need to be hidden and shown conditionally, setting classes on the table - or even the rows - that set the display, rather than manipulating the style property, will perform considerably better. Bottom line: there are quite a few quirks you need to appreciate when working with selections on large data-sets of table rows.

In this case, the best fix is to understand what causes performance bottlenecks with tables and how to refactor your application to avoid them. The support forums ( and #jquery IRC channel on freenode, are a better venue for this type of discussion to continue than the bug tracker as you may be able to have a community member go through your code with you on either.

Thanks for your interest in jQuery!