Closed Bug 71598 Opened 23 years ago Closed 23 years ago

over 75 assertions when I change background/foreground color pref

Categories

(SeaMonkey :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 68208

People

(Reporter: aaronlev, Assigned: attinasi)

References

()

Details

In a debug build, load up www.bottomquark.com, go to Preferences - Appearance - 
Colors. Then change the background or foreground color, and select "always use 
my colors".

You get tons and tons of assertions "Failure to find any context at privided 
key" 'PR_FALSE' file nsStyleSet.cpp.

Marc, are all these assertions really necessary?
Do they mean something important? They don't seem to - the colors change just 
fine. If so, can we remove them?

Aaron
Are these Windows2k specific?
I've found some other assertions when I try to change color prefs, also from
nsStyleSet.cpp. It also throws a lot of "Cannot remove context at provided key"
assertions.

I'm also getting assertion overload when I change font preferences. Just about
anything in the appearance prefs.
No these aren't win2k specific, but at least under Linux all the assertions went
to the console. In Win2k I had to click on ignore a zillion times.
This assertion is to point out when a style context is not in the context cache
and it is asked to be removed. I think that when the crash on pref-chages was
fixed, this assertion probably started showing up. I have to find that crash oin
pref-change bug to see what happened, it had nothing to do with me. I'll check
it out.
Status: NEW → ASSIGNED
Related to bug 68208? I was wong, it has not been fixed yet. I think these are
probably the same problem...
Marking as a dup of bug 68208 - they are the same problem.

*** This bug has been marked as a duplicate of 68208 ***
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
*** Bug 73442 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.