Closed
Bug 374694
Opened 18 years ago
Closed 18 years ago
2.0.0.2 to 2.0.0.3 update hangs on unresponsive update URL for extension
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 308522
People
(Reporter: lech, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Upon performing an update for 2.0.0.2 to 2.0.0.3 checking for extension updates on an unresponsive update URL appeared to cause the entire update process to hang.
Reproducible: Didn't try
Steps to Reproduce:
1. Install an extension with a bad, unresponsive or semi-responsibe update URL
2. Upgrade Firefox from help > Check for updates
3. Watch as the update hangs around while trying to update the extension with a bad or otherwise unresponsive update server.
Actual Results:
I gave it a good 5 minutes, but eventually hit the "quit" button without any ill-effect and 2.0.0.2 upgraded to 2.0.0.3 without any obvious problems. Although the add-on in question (webdev toolbar 1.1.3) still appears to hang when running extension updates even from within firefox.
Expected Results:
After a given amount of time if there's no response or if it is limited, during at least the update phase a timeout should occur. The extension could be temporarily disabled or skipped after this timeout to wrap up the update faster. Or just not having the updater check for updates to extensions or themes at all during the update process. Instead performing it upon a first restart under the newer version.
The best way to reproduce this would be to make a dummy extension with a bogus or ill-responsive update URL which causes this type of hang-up. Needs a timeout.
Updated•18 years ago
|
Component: Software Update → Extension/Theme Manager
QA Contact: software.update → extension.manager
Whiteboard: DUPEME
Updated•18 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•