Every single time I access /admin/build/features I get the following JavaScript alert (after waiting a good 10 seconds for the page to finish initialising)

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.

Script: http://example.com/sites/all/modules/contrib/jquery_update...

After that, if I press continue, the page finally finishes initialising after another couple of seconds, and the Features UI functions fine (though it is very slow - but that's another issue).

Comments

yhahn’s picture

yhahn commented
Status: Active » Postponed (maintainer needs more info)

Is this still occurring on the latest DRUPAL-6--1? It may be related to http://drupal.org/node/704024 which I believe is fixed - bad exports can cause the JS status comparison to time out.

mrfelton’s picture

mrfelton commented
Status: Postponed (maintainer needs more info) » Active

This is still occurring in 6.x-1.0-beta6

yhahn’s picture

yhahn commented
Status: Active » Postponed (maintainer needs more info)

Are you using jquery_update?

Also, do you have access to a JS debugging tool like firebug or the webkit JS console?

mrfelton’s picture

mrfelton commented

I am using jquery_update (6.x-2.x-dev-2009-04-24). Unfortunately my FireBug seems to crash out Firefox every time I launch it! But I'll try and get that fixed and see if there is anything in the console.

mrfelton’s picture

mrfelton commented
Status: Postponed (maintainer needs more info) » Active

So, I got firebug working again - 1.5 seems to be broken for 64bit Ubuntu atm so I had to downgrade it to 1.4.5.

Anyway, I set jquery_update to use the uncompressed version so you can see exactly where the error occurs (jquery.js line 2059):

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.

Script: http://example.com/sites/all/modules/contrib/jquery_update/replace/jquer...

When the error popped up, I hit the debug button, which took me to a console showing:

function (array, results) {
    array = Array.prototype.slice.call(array);
    if (results) {
        results.push.apply(results, array);
        return results;
    }
    return array;
}

With array = Array.prototype.slice.call(array); highlighted.

Anything else I can do to help track this down?

yhahn’s picture

yhahn commented

Thanks for looking into this, I'll try to track it down from here.

socialnicheguru’s picture

socialnicheguru commented

subscribing. I am having the same problem. I do not have jquery_update installed. jquery_update 2x installs jquery 1.3.x I believe.

yhahn’s picture

yhahn commented
Status: Active » Postponed (maintainer needs more info)

Would love to know if this is still happening in the latest Features, especially after this commit: http://drupal.org/cvs?commit=386496

socialnicheguru’s picture

socialnicheguru commented
Status: Postponed (maintainer needs more info) » Postponed

Yes. it is still doing this for me.

I just used the 1.0 version of features.

It is timing out when creating the features page.
It is loading about 400KB for all the views, contexts, etc.

socialnicheguru’s picture

socialnicheguru commented
Status: Postponed » Active

changing status

hefox’s picture

hefox commented

Features export screen really doesn't work for large amount of components; is this the case?

mpotter’s picture

mpotter commented
Status: Active » Closed (duplicate)

Ajax timeouts on large amount of components is being fixed in #1400298: Removing auto-detected components from a feature (UI update, removing Ajax).

adamdicarlo’s picture

adamdicarlo commented
Status: Closed (duplicate) » Active

On a site with, say, 60 features modules, loading admin/build/features can pretty much crash the server, because the JavaScript tries to make the status request for each feature all at once.

So maybe this is the problem that was originally being reported?

mpotter’s picture

mpotter commented
Status: Active » Closed (won't fix)

Sorry, but this is fixed in the 7.x-2.x branch and no backport of the new UI is planned for the 6.x version.

adamdicarlo’s picture

adamdicarlo commented

My problem is a bit different and applies to 7.x-2.x as well; I realized I should open a separate issue:
#1869672: Feature listing page slams Drupal with simultaneous Ajax calls for status requests.