Closed Bug 214777 Opened 21 years ago Closed 20 years ago

Firefox crashes after installing a new theme

Categories

(Firefox :: General, defect, P1)

x86
All
defect

Tracking

()

VERIFIED WORKSFORME
Firefox0.9

People

(Reporter: bugzilla, Assigned: bugzilla)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030731 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030731 Mozilla Firebird/0.6.1

When installing any theme updated for the new skinversion (1.5) Mozilla Firebird
suddenly crashes.

For more info check out this thread at MozillaZine forums:
http://forums.mozillazine.org/viewtopic.php?t=18019

NOTE: On restart of the browser the theme works correctly

Reproducible: Always

Steps to Reproduce:
1. Download or install a new theme (Whether it be via themer or a link)

Actual Results:  
Firebird crashes

Expected Results:  
Firebird should switch to the new theme without crashing.

Talkback did not show up at crash time.
Summary: FIrebird crashes after installing a new theme → Firebird crashes after installing a new theme
OS: Windows 98 → All
Thanks for changing the OS type, Sean.  I can reproduce the problem using both
Linux and XP.
I can also reproduce this using this build:
Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030731 Mozilla
Firebird/0.6.1

...when installing lynchknot's new Rhapsody theme. BTW, that theme has
skinversion 1.5.
Has occured with the following themes:

- Pinball
- Phase
- Rhapsody

All of which have the new skinVersion 1.5
Can be reproduced using Cofee (1.5), too.
Target Milestone: --- → Firebird0.7
Guys, please try a clean profile and repeat the process, this was broken for me
until I did that, now its just having problems changing without a restart
(separate bug).
QA Contact: asa → mpconnor
I always create a new profile when I install a new nightly.  That was the case
when I reproduced the problem.

That said, I am now unable to reproduce the problem. I do recall seeing this
issue until 2003-08-05 or so.  My guess is that between now and then, some
change in the code may have gotten rid of this problem.
I just installed the 0810 build and I have a new crashing website to report -
http://www.svc.com or http://www.svcompucycle.com, both of which are the same
website. Do the developers have any idea where the problem lies?
Sorry, please ignore my comment #7, it was meant for another bug. My apologies...
Unless someone can confirm or reconfirm with a current nightly + clean profile,
I will resolves this as WFM in one day.
I _am_ able to reproduce it, despite the previous comments I've made.  The key
seems to be to specify "Use this theme" when you install a new theme.  By doing
so, I am able to constantly crash the latest nightly (2003-08-11).
I can't crash current nightly using the Install this theme checkbox method either.

If that is the only method that is broken, maybe unhooking it from the backend
is the short term fix, since it doesn't work anyway.
I've been able to reproduce this with 0810 or 0811(can't remember which one),
while installing Phoenity Neo 1.5. The theme installed fine, but once I selected
it, FB crashed. After restarting FB the theme is selected and looks fine and
works normally though, so the crash, at least for me, is a one time thing.
Still, crashes are bad.
I concur with Dai about the  checking Use theme. Lately when I have been
installing themes, I uncheck "Use this theme" it installs fine, checking it will
crash. This happens on a new and old profile

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5b) Gecko/20030811 Mozilla
Firebird/0.6.1+
Can people still reproduce this?
People say they can't reproduce this anymore, so I'm gonna mark worksforme.  (I
think there are still issues like it not actually switching to the new theme
immediately...)
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
or not.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Maybe hiding the "Use this theme" checkbox and setting it false by default would
be a workaround, just for 0.7.
Francesco,

I don't think that's going to make a good workaround.  Yes, you can install a
new theme with the "use this theme" box unchecked, but oftentimes, seleecting
the newly installed theme later will still crash Firebird.

I do see less frequent crashes using 2003-08-27 (Linux), but it still happens. 
I hope the devs can reproduce it frequently enough to be able to debug into it.
Please do 'hide' the 'use this theme' checkmark.
I've seen too many problems with it. I allways recommend 
to uncheck it. As long as dynamic theme switching has problems
(in other words: there are still bugs in bugzilla about it), don't
offer it to the innocent users.
*** Bug 218332 has been marked as a duplicate of this bug. ***
Before we go hiding stuff under boulders... I seem to remember Netscape 6 (I
believe) automatically restarting itself for a new theme switch -- and restoring
the site(s) that the user had previously open in the window. Perhaps this could
be coupled with some kind of notice dialogue (in case the user was logged in a
site, and needed to save some information first) and implemented as a workaround...
Is there any progress on this bug and/or on the other skin bug
http://bugzilla.mozilla.org/show_bug.cgi?id=217410 ??? Both are assigned to
the same person (which is identical with their reporter) and besides four
minor localization issues (which are currently patched) these two are
the only bugs with a FB 0.7 target since 2 or three weeks. 

Does anybody from those who reported a crash still see them? A crash in a 
newbie function like themes is a showstopper but if it's gone then mark this 
Works4me!


-> 0.8 not going to make the cut. 
Target Milestone: Firebird0.7 → Firebird0.8
Update:

It seems to me that this is "fixed" in:

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

I just switched from Qute to about nine other themes without crashing. (I was
careful and didn't check the "Use this theme" box at installation)
Hmm, I guess not, it just crashed when switching from Skypilot to Bluemonkey.
But this was after changing alot of prefs.
*** Bug 220264 has been marked as a duplicate of this bug. ***
Flags: blocking0.8?
if we could reproduce what is causing this crash, it'd be nice to have a fix,
but we don't even have steps to consistently reproduce this.
Flags: blocking0.8? → blocking0.8-
any chance we could turn off dynamic theme switching until this bug gets fixed?
 This is how TB and Seamonkey behave.
-> 0.9
Target Milestone: Firebird0.8 → Firebird0.9
*** Bug 228117 has been marked as a duplicate of this bug. ***
Depends on: 226791
Summary: Firebird crashes after installing a new theme → Firefox crashes after installing a new theme
This only occurs for me when I install several themes.  The first theme
downloads as normal, but the rest never begin to download in the download
manager.  Rather, they are "starting," yet Firefox tells me that the theme had
been installed successfully (and it has).  It tells me this multiple times. 
After installing the 5th or 6th theme, Firefox crashes.  I restart Firefox and
continue downloading with the same results.
I think that's related to the other downloader problems that were just fixed. 
Please retest.
I've managed to get access to a computer for a sec, so nominating one critical
bug for Firefox 1.0.  Actually, I'm surprised no one else has nominated it yet.
 This is a highly visible bug for any user who wants to experience one of
Firefox's most touted features over IE.

Disabling for 1.0 if this can't be fixed is not to my liking, but certainly
better that than displaying such a visible bug to new users.  If only I had time
right now to learn how to code a fix...
Flags: blocking1.0?
On the latest nightly build of this date (current official build is 1.7 RC 2),
when I install a theme, all my tabs will lose their page and say "untitled" but
the url will still be in the address bar. This also makes the IRC window hang at
a white blank screen in all tabs as well.
Does anyone actually have a crash, or is it just the blanking of tabs now?
I don't see any crashes other than 1 separately filed bug for MacOS X (the
number escapes me, I filed it yesterday) and the non-crash tab blanking.
Worksforme. 
Status: REOPENED → RESOLVED
Closed: 21 years ago20 years ago
Resolution: --- → WORKSFORME
No longer depends on: 226791
(In reply to comment #25)
> Hmm, I guess not, it just crashed when switching from Skypilot to Bluemonkey.
> But this was after changing alot of prefs.

Yeah, but the original poster said it was still crashing, and hasn't reported it
working yet.
(In reply to comment #37)
> (In reply to comment #25)
> > Hmm, I guess not, it just crashed when switching from Skypilot to Bluemonkey.
> > But this was after changing alot of prefs.
> 
> Yeah, but the original poster said it was still crashing, and hasn't reported it
> working yet.

Sean?
Flags: blocking-aviary1.0?
I have not had problems with theme-related crashing. This bug is rather outdated
anyway.

Verified
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.