309484 - AMO very slow to load pages and hangs on extension installation

Status: VERIFIED DUPLICATE of bug 305631

(addons.mozilla.org Graveyard :: Public Pages, defect)

Description

[Tracy Walker [:tracy]]

seen on 09/20 and 0921 with Firefox, Mozilla suite and IE (page loading).

-just visit the site and notice the unusually lengthy page load times
-then attempt to install an extension.

tested results: 
hang, confirmation dialog never appears

expected results:
the extension installation confirmation dialog should appear nearly immediately.

Comment 1

[Dave Miller [:justdave]]

Mike Morgan is actually working on this, the existing patches have been getting
posted on a semi-related bug which is now marked FIXED even though those patches
aren't live yet.  This is probably a good place to move the discussion and
patches. :)

Comment 2

[Dave Miller [:justdave]]

*** Bug 309443 has been marked as a duplicate of this bug. ***

Comment 3

[Robert Strong (they/them - no direct email)]

Dave - what are the chances that the bug Mike is working on is going to fix bug
305631 as well? Also, what's the bug number?

Comment 4

[Tracy Walker [:tracy]]

As seen with Linux and Mac builds from this morning 20050923

Page loading is back to normal (not blazing, but not deadly slow either).
Extension/Theme installs work without hang or delay.

Comment 5

[Mike Connor [:mconnor]]

bug 305631 is already on the blocker list, clearing blocking nomination.

Comment 6

[Tim Meader]

Using the latest branch build:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b5) Gecko/20051001 (No
IDN) Firefox/1.4.1 ID:2005100107

Both of the problems mentioned in the description are WFM. Can anyone still
confirm this bad behavior?

Comment 7

[Frank Yan (:fryn)]

Should this be marked as resolved and fixed? because it seems to be directly 
related to Bug 305631 - Extremely long delay when installing an extension 
before confirmation dialog, which is already fixed, i think.

Comment 8

[Dave Miller [:justdave]]

The remaining issues on this are probably covered on bug 310631.

*** This bug has been marked as a duplicate of 305631 ***