When installing custom theme (probably with errors) Firefox crashes.




14 years ago
10 years ago


(Reporter: tyler, Assigned: bugs)


(Depends on: 1 bug, {crash})

1.7 Branch
Windows XP
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)


(Whiteboard: PURIFYME, URL)



14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

I'm trying to create a new theme, however, when I try to install my theme
package Firefox often crashes.

Reproducible: Sometimes
Steps to Reproduce:
1. Create a new theme with errors in rdf
2. Try to install
3. If it didn't crash, click use theme

Actual Results:  
Firefox crashes.

Expected Results:  
Firefox should give an error explaning what is wrong: malformed contents.rdf,
malformed install.rdf, no match between contents.rdf and install.rdf, etc...

I have "Install New Theme 0.3" extension installed.
Error:    32-bit Windows exception

Talkback crash IDs:
TB2296016Q, TB2293665H, TB2293338W, TB2292697W

Comment 1

14 years ago
Theme file is too big to attach: I'm temporarily hosting it here:


14 years ago
Component: Extension/Theme Manager → Layout: Form Controls
Product: Firefox → Core
Version: unspecified → 1.7 Branch

Comment 2

14 years ago
Sorry about the changes - Meant for another bug
Component: Layout: Form Controls → Extension/Theme Manager
Product: Core → Firefox
Version: 1.7 Branch → unspecified

Comment 3

14 years ago
Oh. Crashy thing.
All the talkbacks are different crashes, after different actions.
Keywords: crash, talkbackid

Comment 4

14 years ago
i'm going to file a new bug for *each* of the distinct crashes, as i see them. i
request that no one else file bugs relating to this until i finish.


14 years ago
Depends on: 272879


14 years ago
Depends on: 272880


14 years ago
Depends on: 272881


14 years ago
Version: unspecified → 1.0 Branch

Comment 5

14 years ago
this could be heap corruption. i'm done filing bugs.
Keywords: talkbackid
Whiteboard: PURIFYME


14 years ago
Depends on: 250184
No longer depends on: 272880

Comment 6

14 years ago
Ben:  I remember talking with you about checking themes/extensions at install
time  to make sure they are valid and prevent crash bugs.  Are you already
working on that?  Perhaps we can just mark this a dup or dependant on that.

Comment 7

14 years ago
I just upgraded to Firefox 1.0.1 and this still occurs.
Talkback Crash Id: TB4084882H

Comment 8

14 years ago
that matches bug 272879, please try using talkback-public to look up your own

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.