236689 - crash on alarm acknowledge if calendar and event are brand new

Status: RESOLVED WORKSFORME

(Calendar :: Internal Components, defect)

Description

[Erik Griffin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

When I make a new Event and select as time 24 years older, and select reply all
year, it isn't will work

Reproducible: Always
Steps to Reproduce:
1. Create new Calendar named "Geburtstage"
2. In this Calendar create new Event on Date 6. March 2004
   - in Register "Event":
     - set "Title" to "Hans Wurst"
     - set "Starts" to "06.03.1986"
     - set "Ends" to "07.03.1986"   
     - select "This Event lasts all day."
     - set "Note" to "Geburtstag - Wurst, Hans"
     - select "Private"
     - select "Alarm" to "5 Days before the event starts"
     - set "Event Status" to "Tentative" 
     - set "Categories" to "Birthday"
     - set "Calendar File" to "Geburtstage"
   - Change Register to "Reccurrence":
     - select "Repeat every" to "1 Year"
     - select "Forever"
3. Press OK
4. Click to "Acknowledge" on the "Mozilla - Calendar Alarm - Alarm" Window
5. Mozilla does not react any longer, the CPU is working at full capacity to 100%

Comment 1

[Justin Wood (:Callek)]

My guess is this has to do with the epoch time, might I ask if there is any
particular reason that you are setting the event for 1986 instead of now, when
you installed the calendar...and from now on to repeat every year?

Comment 2

[Erik Griffin]

Ich stelle deshalb das Datum auf 1986, weil Hans Wurst 1986 
geboren wurde. Hat den Vorteil, dass ich sofort sehe wann er 
geboren ist und wie alt er wird. Der Kalender dürfte deshalb 
aber nicht abstürzen oder?
------------------------------------------------------------
I set the date to 1986, because Hans Wurst was born 1986.  
It has the advantage that I see immediately when it am 
born and he become as old. The calendar might however 
not fall therefore or?

Comment 3

[Jussi Kukkonen]

Confirming, I get a 'Memory could not be "written"' error. 

It seems that the calendar has to be new - creating a similar event on an
existing calendar file worked?

Comment 4

[Jussi Kukkonen]

Tested a little more. It's not about 1986, it's not about recurrence. This is
what is needed for the crash:
- open Calendar
- create new calendar
- create new even with an alarm that fires right away
- try to ack

It seems that a call to OEIICal.modifyEvent() crashes. The calendar file is ok.

Comment 5

[Jussi Kukkonen]

dammit. Forgot to update summary.

Comment 6

[Jussi Kukkonen]

*** Bug 217556 has been marked as a duplicate of this bug. ***

Comment 7

[Alan Batie]

I suspect it's any expired alarm; I created a remote calendar to play with, a
week or so ago with a test event for friday the 3rd.  Someone came in to ask
about it today, so I fired up the calendar and was reminded of the event. 
Later, I went to Ack it and the entire mozilla app crashed.  1.7.3 built out of
the FreeBSD ports.

Comment 8

[Joey Minta]

We replaced the alarm dialog and the entire structure behind this.  I've never crashed with alarms.  Resolving as WFM.

Comment 9

[Marcia Knous [:marcia]]

Mass move of libxpical bugs to the Internal Components, per ctalbert.

Comment 10

[Reed Loden [:reed]]

The bugspam monkeys have been set free and are feeding on Calendar :: Internal Components. Be afraid for your sanity!