Created attachment 49422 [details]
back trace

Steps to reproduce?  Just editing a plain groupwise appointment that you had 
previously created.  If not, what did you change, where did the original 
appointment come from, how did you start the edit process? 
 

(In reply to comment #2)
> Steps to reproduce?  Just editing a plain groupwise appointment that you had 
> previously created.  If not, what did you change, where did the original 
> appointment come from, how did you start the edit process? 
>  

I just sent a test appointment (event) out to you and myself for the 116193 bug.
I then went to the calendar view and double clicked on the appointment to edit
it. That is when I receive the crash.

Amended steps to reproduce:

(1) Click on button to create a new event.
(2) Put in a subject
(3) Choose the reminder option
(4) Switch to the Attendees tab and using the name field I usually add myself as
an attendee and someone else. I then send the appointment.
(5) When prompted what calendar to place the appoitment in, I choose groupwise.
(6) Once the appoitment came into the calendar, I can usually get it to crash by
double clicking on the appointment, but sometimes it will allow me to get in and
edit it. I can then make a change to it and then when accepting those changes,
it will sometimes crash.

Still can't reproduce this.   
 
When you say you are waiting for it to arrive, is that the invitation to 
yourself in the Mail view?   
 
If you are then accepting that, do you get two copies of the appointment in 
your Calendar and it is when editing one of those that crashes? 

(In reply to comment #5)
> Still can't reproduce this.   
>  
> When you say you are waiting for it to arrive, is that the invitation to 
> yourself in the Mail view?   

Yeah

> If you are then accepting that, do you get two copies of the appointment in 
> your Calendar and it is when editing one of those that crashes? 

Yeah, and usually the one the come in from accepting it in my inbox. And it
doesn't crash all of the time. Seems like about 50% of the time.

I am ok if we lower the severity on this since it seems hard to reproduce. I
will see if I can narrow it down a little.

The calendar view layout code is non-deterministic so you wouldn't really know 
which one is which.  "50% of the time" would be about right.  I just have to 
reproduce this myself then I can see where the code is going to create a 
dangling pointer that causes the crash.  Downgrading to Major in the meantime. 

Fixed a bunch of dangling pointers just now. Please reopen if it's still there.

Fixed