Edgewall Software
Modify

Opened 16 years ago

Closed 14 years ago

Last modified 13 years ago

#7837 closed defect (worksforme)

jquery.js Unresponsive with Mozilla 3.0.4

Reported by: trac@… Owned by:
Priority: normal Milestone:
Component: version control/browser Version: 0.11.2.1
Severity: minor Keywords:
Cc: Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Clicking on any link on a Browse Source page with at least 1100 files or directories the following error is generated in Mozilla Firefox 3.0.4. This includes any of the Trac navigation such as Wiki, Timeline, etc. Stopping the script does load the next page. This error does not seem to occur in IE6.

A script on this page may be busy, or it may have stopped responding. 
You can stop the script now, or you can continue to see if the script will complete.

Script: http://noc.localnet.sys/trac/chrome/common/js/jquery.js:11

Attachments (0)

Change History (7)

comment:1 by Christian Boos, 16 years ago

Milestone: not applicable

Well yes, hopefully they'll fix that in newer version of Mozilla. No other browser I've tested has this behavior.

Upgrading jQuery to 1.3.1 also doesn't improve anything.

(keeping the ticket open as a 3rd party issue)

comment:2 by Christian Boos, 16 years ago

It's even more funny on a page which holds 10000 rows (right, it's my test page for #5782). Firefox's memory keeps going from 400M to 800M and back, each second, CPU at 100%. This goes on since 5 minutes now … ok finished. Thank you Firefox for not crashing ;-)

#6101 would definitely help.

comment:3 by guillermog@…, 16 years ago

Same problem here,

FF 3.0.6

problem seems to be in jquery.js:11 (1.2.6)

comment:4 by Christian Boos, 15 years ago

Milestone: not applicable0.12.1
Severity: normalminor

FF 3.5 is still very slow when leaving my 10000 entries test page, but at least doesn't show an error. It's now more like 30s than 5 minutes though, which is probably bearable.

I always thought this could be a FF bug, as in Chrome leaving that page is nearly instantaneous. But when testing with Safari, it seems that there's indeed a 1-2 seconds delay that could be attributed to Javascript. So maybe there's something we can optimize…

comment:5 by anton, 15 years ago

Perhaps update to jQuery 1.3.2 which is the actual one would be a good idea (even if its not the problem here perhaps) … but to be up to date, since most people use 1.3.2 now

in reply to:  4 comment:6 by Christian Boos, 14 years ago

Milestone: next-minor-0.12.x
Resolution: worksforme
Status: newclosed

Replying to cboos:

FF 3.5 is still very slow when leaving my 10000 entries test page, but at least doesn't show an error. It's now more like 30s than 5 minutes though, which is probably bearable.

No longer a problem with FF 4.0b10.

comment:7 by anonymous, 13 years ago

I am getting this problem with jquery 1.6.4 and FF 7.0.1 Linux … stopped responding. You can stop the script now, or you can continue to see if the script will complete. Script: http://www.......com/JS/jQuery.js:3

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.