Closed Bug 171785 Opened 23 years ago Closed 23 years ago

6 Assertions in nsStaticNameTable::Init() during startup

Categories

(Core :: CSS Parsing and Computation, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: kinmoz, Assigned: caillon)

References

Details

Attachments

(1 file)

I've been seeing 6 assertions on startup: ###!!! ASSERTION: Entry already exists!: 'entry->mKey == 0', file y:/mozilla/xpc om/ds/nsStaticNameTable.cpp, line 139 Break: at file y:/mozilla/xpcom/ds/nsStaticNameTable.cpp, line 139 ever since the morning of 09/26/02. All having to do with the key "outline". A quick look at all the checkins between 09/25 and 09/26 with: http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=09%2F25%2F2002+08%3A00%3A00&maxdate=09%2F26%2F2002+08%3A00%3A00&cvsroot=%2Fcvsroot and it looks like the fix for bug 117500 may be related?
Summary: 6 Assertions → 6 Assertions in nsStaticNameTable::Init() during startup
Yeah this is mine. Sorry about these. Actually I think this patch already has r=dbaron sr=jst since this was in my patch in bug 117500 but for whatever reason I somehow managed to not check this part in. The only other change in this patch is a silly goof of over c&p'ing in the outline properties...
Status: NEW → ASSIGNED
Comment on attachment 101165 [details] [diff] [review] Fix Yup, this gets rid of the assertions. Thanks!
I see the assertions, but I also crash... Does anybody else crash, or am I hitting something else?
Comment on attachment 101165 [details] [diff] [review] Fix Since the original patch used the CSS_PROP_NOTIMPLEMENTED macros for the props changed in this patch and were r=/sr='d already, I'll give an r/sr=kin@netscape.com on the "outline" c&p corrections ... lets get this puppy in. stephend, I'm not seeing a crash, just the assertions.
Attachment #101165 - Flags: superreview+
*** Bug 171326 has been marked as a duplicate of this bug. ***
Checked in. The only thing I can think of is I undid a few changes in the wrong file by accident, saved without realizing and then didn't notice before landing. Anyway, it's been righted now.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: