302711 - Attempting to close the browser while downloading a theme results in non-functional 'duplicate'

Status: RESOLVED DUPLICATE of bug 266117

(Toolkit :: Add-ons Manager, defect)

Description

[Ben Small]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050729 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b4) Gecko/20050729 Firefox/1.0+

If you try to close the browser while downloading a theme, an empty duplicate
entry for the theme will appear in the Theme Manager [immediately above the
normal entry].

Reproducible: Always

Steps to Reproduce:
1. Go to the Firefox themes site [https://addons.mozilla.org/themes/]
2. Choose any theme that is compatible with Deer Park (i.e., miniFox 0.4) and
install it by clicking on the "Install" button on the site.
3. While the theme is downloading, close the browser entirely. [Close all the
windows]
4. When you get the "Download in progress" dialog, tell it "Don't Exit".


Actual Results:  
There will be two entries in the Theme Manager for the theme:

[The second entry] The regular entry for the theme

AND

[The first entry] An empty, greyed-out (at least, I think it's greyed-out) entry
(no preview) that can be selected just like any other entry, except you can't do
anything with it - uninstall, use, etc.


Expected Results:  
There should be only one entry for the theme, namely, the normal entry.

Comment 1

[Joshua B.]

This also happens in Firefox 1.5 beta 1 on Windows XP. I experienced this when
attempting to install a theme that took up 99% of the CPU for about five
minutes. After a while of this nothing was happening with 0% activity by Firefox
on the CPU, yet the application still wasn't responding. Forcing it to quit and
then relaunching Firefox showed an empty theme as described by the initial poster.

Comment 2

[Przemyslaw Bialik]

Looks like a duplicate of Bug 266117.

Comment 3

[Ben Small]

(In reply to comment #2)
> Looks like a duplicate of Bug 266117.

Not exactly...

Bug 266117 deals with the Extension Manager, whereas this deals with the Theme
Manager.  Same problem, different component.

Comment 4

[u88484]

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