Closed Bug 12703 Opened 25 years ago Closed 25 years ago

[Dogfood][PP] Sorting tree when row selected causes crash

Categories

(Core :: XUL, defect, P3)

PowerPC
Mac System 8.6
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: hangas, Assigned: alecf)

References

Details

(Whiteboard: [PDT+])

Steps: Launch apprunner, choose Address Book from Tasks Menu, select an address book, (need cards in address book so if none are there add them), click on the name column to sort. At this point everything is fine. Now select any card, and click on name column again...crash.
Blocks: 11091, 12176
Severity: normal → critical
Assignee: trudelle → hyatt
I'm taking a guess here, but I just saw this same crash about 30 minutes ago and it looked to be similar to the delete crash. I'm going to reassign to hyatt because this is a selection bug.
Status: NEW → ASSIGNED
Target Milestone: M10
Blocks: 12716
Blocks: 12669
phillip, can you check if this is Mac only.
Summary: [Dogfood] Sorting tree when row selected causes crash → [Dogfood][PP] Sorting tree when row selected causes crash
does not happen on linux 2.2, build 1999-08-30-02 can't test win32, because the past few win32 builds have been very unstable with forms, and i can't add cards to the address book. (cpratt has a bug open on that.) adding [PP] designation.
mass targetting m11
No longer blocks: 12176
My hands have deteriorated to the point where I can no longer type. I need help. If you think you can fix this bug on your own, please take it away from me. If you'd like to volunteer to be my hands for a specific bug, then I'll be happy to come up to your cube and sit with you and fix the bug (assuming you have the patience for that).
I will be your hands here.
Assignee: hyatt → putterman
Status: ASSIGNED → NEW
I'll take this.
Blocks: 15008
Whiteboard: [PDT+]
Putting on PDT+ radar.
Assignee: putterman → alecf
I think I may know what's going on here, and it may have to do with some stuff I'm implementing.
Status: NEW → ASSIGNED
Alec, are you planning a fix before the tree closes tonight?
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I believe the problem is because we're holding onto the content nodes we are selecting, and when you do a sort, it blows away those nodes... fixed thanks to putterman's work tracking down the problem
QA Contact: phillip → claudius
Resetting QA Contact.
Status: RESOLVED → VERIFIED
VERIFIED fixed for 1999120113 builds
You need to log in before you can comment on or make changes to this bug.