Crash on this testpage

Discussion of bugs in Seamonkey
Post Reply
mw22
Posts: 2379
Joined: November 19th, 2002, 5:37 pm

Crash on this testpage

Post by mw22 »

Recent Mozilla builds seem to crash when you click three times on one of the anchors. Link:
http://home.hccnet.nl/m.wargers/test/mo ... m#userfile
Older ones don't seem to work.
Seems to happen only in combination with position:absolute and input type=file.
Gabor Bukovics
Posts: 26
Joined: December 31st, 2002, 10:12 am
Location: Budapest, Hungary

Post by Gabor Bukovics »

Me too.

Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030218
herman
Posts: 1034
Joined: November 7th, 2002, 3:45 pm

Post by herman »

Also crashing with Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.3b) Gecko/20030221
Talkback-IDs TB17382653Y, TB17383217G

Did you file a bug on this?
Do you think bug 194362 is related?

herman
mw22
Posts: 2379
Joined: November 19th, 2002, 5:37 pm

Post by mw22 »

No, I didn't file a bug. I don't know anything about the inner workings of Mozilla. It just happens that I stumbled into this bug. The bugzilla system is scaring me off a little. Anyway, I couldn't find anything related in there
maybe bug 194362 is related. It looks a bit like it. Although I don't use frames or anything else. I just toggle the display of an absolutely positioned input type=file button.
User avatar
bzbarsky
Posts: 478
Joined: November 5th, 2002, 1:36 pm

Post by bzbarsky »

herman wrote:Do you think bug 194362 is related?


It's not. This crash is happening because we're trying to clear out style data on a deleted rulenode:

#0 nsCOMPtr<nsIStyleRule>::get (this=0xdddddde5)
at ../../../../dist/include/xpcom/nsCOMPtr.h:632
#1 0x4146060a in int operator==<nsIStyleRule, nsIStyleRule> (lhs=@0xdddddde5,
rhs=0x863076c) at ../../../dist/include/xpcom/nsCOMPtr.h:1162
#2 0x412c14f0 in nsRuleNode::ClearCachedData (this=0xdddddddd, aRule=0x863076c)
at /home/bzbarsky/mozilla/xlib/mozilla/content/base/src/nsRuleNode.cpp:577

The patch in bug 171830 changes things a bit, but not significantly In any case, I've filed bug 194615 on this
Post Reply