Closed
Bug 128260
Opened 23 years ago
Closed 23 years ago
crash when apply classic theme twice
Categories
(Core Graveyard :: Skinability, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: chris+bugzilla, Assigned: bugs)
Details
(Keywords: crash)
Attachments
(1 file)
|
6.31 KB,
text/plain
|
Details |
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:0.9.8+)
Gecko/20020227
BuildID: 2002022708
This is probably a dupe, or at least closely dependent on another bug, but none
of the other theme switching crashes is triggered by the same steps as what I
describe here.
Dupe candidates are bug 120355 and bug 121963.
If someone can point me to instructions to produce a stack trace under OS X, I'd
be happy to provide one.
Reproducible: Always
Steps to Reproduce:
1. Start with classic theme
2. Switch to modern theme
3. Switch to classic theme
4. Switch to classic theme again
Actual Results: crash
Expected Results: nothing, since that is already the current theme
> If someone can point me to instructions to produce
> a stack trace under OS X, I'd be happy to provide one.
Most crashes will generate a stack trace if you have the
box "Log crash information in ~/Library/Logs" checked in
Console.app's preferences.
Failing that, if you have the developer tools installed,
you can get a stack trace by running Mozilla in gdb. See
e.g. comments #4 and #6 to bug 120863, or for background,
http://developer.apple.com/technotes/tn/tn2032.html#Section2.
| Reporter | ||
Comment 2•23 years ago
|
||
Attached crash log, using Console.app logging as suggested above.
Comment 3•23 years ago
|
||
WFM, 10.1, RC1
-Brett
Also WFM using RC1. This bug probably occurred when dynamic theme switching was
enabled; it isn't now.
Resolving WFM for now.
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•