Since the migration of d.o to D6 there have been some reports that certain pages are causing firefox browser to freeze up, crash, or throw an error.
The main culprit, and one that I have experienced myself (I've had to restart my browser several times after visiting) is the module list page
I have tested this Google Chrome and IE with no error, so it seems to be a uniquely Firefox issue.
See the thread here: http://drupal.org/node/384260
Could someone please check this out.
thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #36 | jquery.js.txt | 97.97 KB | damien tournoud |
| #35 | 390494-slow-unbind-jquery2.patch | 60.89 KB | hass |
| #34 | 390494-slow-unbind-jquery.patch | 61.02 KB | damien tournoud |
Comments
Comment #1
WorldFallz commentedI can confirm this as well-- I thought perhaps it was just my install. But I reinstalled firefox and the module alpha list page repeated crashes the browser so that i have to go in and manually kill the firefox process to restart. The weird thing is, it displays the module alpha list page fine-- it only crashes when i try to close the page.
Comment #2
mjohnq3 commentedSame thing with Firefox 3.0.6. When I try to use the Back button to navigate I receive the following error from Firefox:
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://drupal.org/files/js/1c70a2434563f432f75f967e69228157.js:13
Comment #3
kbahey commentedI can also confirm this on Firefox 3.0.6 on Linux.
The page displays fine, but when I try to close the tab, Firefox hangs and then gives the dialog box of the script hanging after many seconds.
Comment #4
WorldFallz commentedprobably related to the upgrade-- so going to follow gabor's instructions for bug reporting.
Comment #5
WorldFallz commentedAlso reported on http://drupal.org/node/381826 (marked as duplicate since this has more comments).
Comment #6
webernet commentedI've noted this on various pages as well. I had noticed this immediately following the upgrade and made killes and dww aware of it at that time. It's apparently only an issue on Firefox.
Prior to the JS aggregator being enabled, jquery.js was being referenced in the hung script error.
Comment #7
aterchin commentedWhoops, had to edit this comment... didn't realize this was about Drupal.org. I'm having same probs on my own site....
Comment #8
candelas commentedi can confirm that it is after the upgrade because i have been redading last month this site.
i remember one day that you stoped the site for upgrading.
i was consulting lots the module page and after the upgrade, i started to get this messages.
my browser (firefox3 on ubuntu hardy) didnt crash normally because i told to stop the script.
now i am getting that also on some pages on my site and i think it is because i have the l10n_client-6.x-1.6 that uses jquery to get strings to transllate.
thanks people to keep drupal :)
Comment #9
alexanderpas commentedalso happening now on FireFox 3.0.7 on Windows
I can browse the page, but licking a link closing or back/forward will create hang.
Comment #10
WorldFallz commentedAnother report of the same: http://drupal.org/node/394810
Comment #11
tamhas commentedI do hope someone decides to pay attention to this since it **really** slows down browsing for modules. As we are in active sitebuilding, I am doing a lot of looking for new modules and going to download modules that I found earlier. Except for this problem, my experience has been that leaving a tab on the alphabetical list page and then searching for the name is a very fast way to find a module and thus get to its full page. Depending on the module, this is not always easy with the regular search since too many candidates come up if the name of the modules is some common words.
Comment #12
Timo.Kissing commentedSince jquery is delivered packed here I can not verify it, but I had a similar problem on one of my drupal pages and the solution was applying http://dev.jquery.com/changeset/5758 to the jquery.js - maybe that will help here too.
Comment #13
simon.males commentedI've taken a few steps to replicate this and confirm that the 1.2.x branch of jQuery solves the problem.
Firstly I downloaded the page in question locally via wget:
wget -O bad_page.html http://drupal.org/node/206666Inserted the base element into the document head.
<base href="http://www.drupal.org" />Next:
Reload page, Firefox loads fine.
Comment #14
Timo.Kissing commentedChanging priority to critical.
This can be fixed in 5 minutes, alas noone seems to care. I lost more worktime due to this than those 5 minutes, I am sure the same is true for more than 1 person.
Comment #15
gregglesFor what it's worth, switching to Firefox3.5beta fixed the problem for me.
Comment #16
damien tournoud commentedThis is a core issue, then. It has to be fixed in core.
For what is worth, it seems that Drupal 6 ships with the latest version of the jQuery 1.2 branch (1.2.6). I see no change in jQuerye Subversion repository after the release of 1.2.6, and [1] doesn't seem to apply on the 1.2.x.
Comment #17
attiks commentedFor what it's worth, I tested http://drupal.org/node/206666 with FF3.0.10 without any problems (loads in 11sec)
Comment #18
tamhas commentedThe delay is not in loading that page, but in following the links on that page to the individual modules. Curiously, going to that page and clicking on Back seems to also produce the symptom. For me, this is the only page on the entire Drupal site exhibiting this behavior. I haven't trolled drupal.org extensively since this came up, but have done a fair number of module and theme upgrades, looking at release notes, creating new issues and following responses, etc.
Comment #19
attiks commented#18, I tested it and got a script time-out as well :/
Comment #20
chadhester commentedSince I've experienced this on my own site as well, I figured I'd mention that the issue is even worse on a site with about 50 enabled modules when visiting the site's Permissions page. Tons of checkboxes take a while to render, it seems. I too often see the script-timeout messages and have since lengthened the timeout in about:config, which only slightly helps.
Comment #21
Timo.Kissing commentedWill this ever be fixed? Obviously noone working on d.o. uses the site with FF3, but there are others out there who do. And we value our time. Waiting several seconds everyone I navigate away from or close a d.o. site is not fun. If I had any say in it, I would move the whole project to a different CMS by now just to stop wasting so much time.
Comment #22
damien tournoud commentedThis is a jQuery issue, there is nothing we can do about it. Most of us (the "ones working on d.o.") are using Firefox 3, and I haven't experienced this issue anywhere except some very heavy pages. There is nothing to do, except reducing the size of those pages.
Thanksfully the "Alphabetical list of all modules, by core version" page is not the most used page in drupal.org ;)
Comment #23
gerhard killesreiter commentedThere is apparenlt no clear solution to the problem. Getting pissy won't solve it either.
Comment #24
gerhard killesreiter commentedAh, that was some cross posting.
I sure want to see it fixed, but yes, it is not critical at all.
Comment #25
Timo.Kissing commentedOf course you can do something about it. Scroll up the page, I posted the jQuery patch that will fix this problem. Apply it to the jquery file on this server and this problem is GONE! (BTW: Both at work and from home I have the problem on almost every api.d.o page and on all but the smallest d.o pages).
In any case, I will not recommend Drupal for any further projects. You guys are way to fast with the "won't fix" button.
Comment #26
damien tournoud commented@Timo.Kissing: please calm down. Drupal is using jQuery 1.2.6, which is the latest version of the 1.2 branch. The patch you are linking has only been released in the 1.3 branch.
I said in #16, that I see no change in the 1.2 branch since the release of 1.2.6. Looking again, I'm not sure where is the 1.2 branch, as the
http://jqueryjs.googlecode.com/svn/branches/1.2doesn't really seem to match what you can find in 1.2.6.Anyway, this is a Drupal core bug. It needs to be fixed there, before being deployed on drupal.org.
Comment #27
damien tournoud commentedComment #28
simon.males commentedSo it seems that the 1.2 branch does not exist and thus jQuery 1.2.6 is unsupported.
If that is the case, should then Drupal maintain/fork jQuery 1.2.6 ?
Comment #29
cszalwin commentedFYI
FF 3.5 beta does not fix this problem completely, although FF response is considerably improved
For the case where a custom menu has 377 items see http://drupal.org/node/291156#comment-1751950 ff.
Chris
Comment #30
tamhas commentedReleased version of FF3.5 fixes the problem for me on the Alphabetic List of Modules page. Pretty zippy, even. Not instantaneous, but just a brief pause.
Comment #31
WorldFallz commentedYep, I can confirm that ff3.5 fixes this in the 2 places I encountered this problem on every single visit:
Comment #32
quicksketchThe culprit on Drupal.org is Google Analytics module, which makes a unique binding for EVERY link on the page. Meaning that if there are 10,000 links on the page (like there are on http://drupal.org/project/usage), then jQuery has to loop through all 10,000 DOM elements and unbind the event. Rather than patching jQuery, we could also just fix this bug in the Google Analytics module. See #336924: Massive page rendering slowdown with many links.
Comment #33
hass commented+, Could one of you subscribers confirm the slowdown with Firebug and other debugging and developer tools disabled, please?
Comment #34
damien tournoud commentedPatched jQuery 1.2.6 with http://dev.jquery.com/changeset/5758, for testing purposes.
Comment #35
hass commentedPatch in #34 cannot applied. New patch attached.
Comment #36
damien tournoud commentedNate told me that the patch above doesn't seem to solve the issue with GA. Here is the patched non minified non packed version. Let's see if we can debug where the issue really is.
Comment #37
mischan commentedWe have the same problem on our site for a while now on several "bigger" pages... the behaviour is pretty much the same as stated throughout the issue comments... especially when going back in the history, which seems to be the least intuitive for our users... also I wouldn't say that there are drastic changes in the different browser versions (Chrome, FF30x, FF35, IE8), on every page where the slow-down happens you can "feel" complete inactivity of the browser anywhere between 0,5-1 sec (in bad cases it is way above). Btw, we do not use GoogleAnalytics. I will give the last attachment a try as soon as I start working tomorrow.
Comment #38
Chad_Dupuis commentedMostly subscribing,
but, does anyone with this issue have the drupal.js file loading twice? I've seen other complaints about this delay with various subject lines. On my site (a test version in the midst of an upgrade to d6) has this delay and I see the following within every page (although the delays are longest in the admin sections):
The problem is I've search every line of code on the site to see where the second one is loading from and cannot seem to find it. So I cannot see if this is related to the delay....
Please excuse/ignore me if this is off subject, just curious if others are getting this as well...
Comment #39
damien tournoud commented@Chad_Dupuis: those are two different javascript files (jquery.js and drupal.js).
Comment #40
damien tournoud commentedProbable duplicate: #528264: "unresponsive script", jquery.js, only @ modules page.
Comment #41
Starminder commentedsubscribing.
Comment #42
davidwhthomas commentedsubscribing
Comment #43
ycimlynn commentedsubscribing
Comment #44
krysgeek commentedsuscribing
Comment #45
jayson commentedsubscribing
Comment #46
ycwjjjj commentedsuscribing
Comment #47
westbywest commented@hass:
I tried applying your 2nd patch to misc/jquery.js on a D6.12 site, no Google Analytics in use, and I still get this error dialog in FF3.5.6 for Ubuntu when viewing the module list.
No such problem when viewing the module list in Chromium.
Comment #48
klonosI just started having this issue yesterday. Very odd...
Drupal.org home page doesn't crash. The module's main page doesn't crash either, but as soon as I select to visit one random module's page I get the crash.
I am testing latest firefox dev builds. Right now I use 3.7a1pre (latest nightly build 20100128) and I upgrade almost daily. I have three profiles with different addons installed and it only happens in one of them. So, it is not the firfox build that has the issue, otherwise all other two profiles would crash as on me well.
I tried disabling all plugins from the profile with the crashes except MR Tech Toolkit 6.0.4 and I still get crashes. It is not specific to Mr Tech Toolkit, because I have the same version installed in the other two profiles and they don't crash.
I will try reverting to an earlier nightly build (a few days back) and see if I still get the crashes. I will report as soon as I test.
Comment #49
klonos...well I emptied my firefox profile's cache for today only and deleted all cookies. Restarted. Re-enabled previously disabled addons. Restarted.
Now I don't get crashes anymore. I hope this whole process and information from my previous post and this one will help people in the future. Also let's hope that someone someday figures out what causes all this mess.
Comment #50
abaddon commentedstill have this with latest firefox on linux and the patch above applied, firebug & the rest disabled, also had it on a clean firefox profile with no addons, im on debian
its somewhat related to lots of links on the page, administration menu causes it for me on all pages its active, also dpm() from devel
are there really so few with this problem or everyone else just ignoring it ? maybe its something in our setup?
Comment #51
kristen polSubscribing
Comment #52
candelas commentedi subscribe that happens with pages width many links.
ubuntu 9.04, firefox 3.019
Comment #53
micheleannj commentedsubscribing.
Comment #54
xjmTracking.
Comment #55
druderman commentedTracking.
Comment #57
hass commented#35: 390494-slow-unbind-jquery2.patch queued for re-testing.