Closed
Bug 12711
Opened 25 years ago
Closed 25 years ago
[CRASHER]gfx select crashes after 'onclick' event
Categories
(Core :: XUL, defect, P3)
Core
XUL
Tracking
()
VERIFIED
FIXED
People
(Reporter: phillip, Assigned: joki)
References
Details
Attachments
(3 files)
Overview Description: gfx select crashes after 'onclick' event and a few mouse clicks. Steps to Reproduce: 1) launch apprunner. 2) make sure GFX widgets are turned on via user_pref("nglayout.widget.mode", 2); 3) load the attatchment to come 4) single click (and immediately let go of the button) on the select/dropdown box 5) single click on either option (the select disappears) 6) single click again in the same spot. Actual Results: SIGSEGV on linux and nt, no crash on mac. (but the gfx select disappears across platforms) Expected Results: The select should not disappear, and no crash should occur. Occurs on Apprunner on these Build Dates & Platforms: 1999-08-27-05-M10 RedHat Linux 6.0 (GNOME/enlightenment) 1999-08-27-09-M10 WinNT 4.0 sp5 1999-08-27-12-M10 MacOS 8.51 Stacktrace: to come (it seems cyclone is down, no talkback id today)
Updated•25 years ago
|
Assignee: trudelle → kmcclusk
Comment 3•25 years ago
|
||
not an xptoolkit widget, reassigning to kmcclusk
Updated•25 years ago
|
Assignee: kmcclusk → rods
Comment 4•25 years ago
|
||
Rod, reassigning to you
Updated•25 years ago
|
Assignee: rods → mjudge
Comment 5•25 years ago
|
||
this happens with the input select because the text selection is getting invoked when you select an item in the list (a little confusing). I can duplicate this by selecting some text and then pressing a button, sometimes I have to do it more than once. reasssigning to mike.
Comment 6•25 years ago
|
||
umm joki event again. the frames are destroyed and messages arive. here is a mini stack trace i have: nsGenericElement::GetParent(nsIContent * & 0x00000000) line 723 + 24 bytes nsHTMLSelectElement::GetParent(const nsHTMLSelectElement * const 0x02be5510, nsIContent * & 0x00000000) line 163 + 18 bytes nsCSSFrameConstructor::FindPrimaryFrameFor(nsCSSFrameConstructor * const 0x02bc54d0, nsIPresContext * 0x02dfd910, nsIFrameManager * 0x02bc5a70, nsIContent * 0x02be5510, nsIFrame * * 0x02bc55fc) line 7620 StyleSetImpl::FindPrimaryFrameFor(StyleSetImpl * const 0x02bc5440, nsIPresContext * 0x02dfd910, nsIFrameManager * 0x02bc5a70, nsIContent * 0x02be5510, nsIFrame * * 0x02bc55fc) line 966 FrameManager::GetPrimaryFrameFor(FrameManager * const 0x02bc5a70, nsIContent * 0x02be5510, nsIFrame * * 0x02bc55fc) line 238 + 47 bytes PresShell::GetPrimaryFrameFor(const PresShell * const 0x02bc55a0, nsIContent * 0x02be5510, nsIFrame * * 0x02bc55fc) line 1804 + 32 bytes PresShell::HandleEvent(PresShell * const 0x02bc55a4, nsIView * 0x02bd56a0, nsGUIEvent * 0x0012fbf8, nsEventStatus & nsEventStatus_eIgnore) line 1979
Updated•25 years ago
|
Severity: normal → critical
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 9•25 years ago
|
||
Adding waterson to cc. Chris, Vidur said you were going to look into nulling out parent refs when the content tree goes away. This seems like a case where we're hitting a bad parent ref on content. Is this anywhere near the stuff you were looking at? Or is Vidur just nuts.
Comment 10•25 years ago
|
||
giving me rest of phillips open qa contact bugs, sorry for spam
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 11•25 years ago
|
||
I believe waterson fixed the bad parent pointer thing a while back. I'm going to mark this fixed unless someone proves me wrong.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 12•25 years ago
|
||
verified
Comment hidden (collapsed) |
You need to log in
before you can comment on or make changes to this bug.
Description
•