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)
Tracking
()
VERIFIED
FIXED
M11
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.
Updated•25 years ago
|
Assignee: trudelle → hyatt
Comment 1•25 years ago
|
||
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.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Target Milestone: M10
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.
Comment 4•25 years ago
|
||
mass targetting m11
Comment 5•25 years ago
|
||
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).
Updated•25 years ago
|
Assignee: hyatt → putterman
Status: ASSIGNED → NEW
Comment 7•25 years ago
|
||
I'll take this.
Assignee | ||
Updated•25 years ago
|
Assignee: putterman → alecf
Assignee | ||
Comment 9•25 years ago
|
||
I think I may know what's going on here, and it may have to do with some stuff
I'm implementing.
Assignee | ||
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 10•25 years ago
|
||
Alec, are you planning a fix before the tree closes tonight?
Assignee | ||
Updated•25 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 11•25 years ago
|
||
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
Comment 12•25 years ago
|
||
Resetting QA Contact.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 13•25 years ago
|
||
VERIFIED fixed for 1999120113 builds
You need to log in
before you can comment on or make changes to this bug.
Description
•