292703 - Flood of alarms / Crash when recurring event initial date moved back in time

Status: RESOLVED DUPLICATE of bug 229916

(Calendar :: Internal Components, defect)

Description

[silcndude]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050418 Firefox/1.0.3 (Debian package 1.0.3-1)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050418 Firefox/1.0.3 (Debian package 1.0.3-1)

Calendar alarm code is highly buggy and apparently untested.  This
crash-inducing bug is one of many similar issues I have discovered.  In some
ways it seems a little silly to file a bunch of bugs because the alarm code is
alpha quality at best and most bugs would probably disappear with a day of
casual code review and testing.

Reproducible: Always

Steps to Reproduce:
1. Create an event that repeats fairly regularly (daily, bi-weekly, etc.)
2. Add an alarm to the event
3. Move the initial event date back a bit (say one month earlier than today's date)

Actual Results:  
Flood of alarm windows pop up, CPU at 100%, effectively crashes Calendar or must
kill it to restore system.

Expected Results:  
When moving a recurring event back in time, disable the alarm for all events up
until the current date/time.

In general, old events past a certain age should not cause alarm triggers
regardless.  This causes problems when a user is out for a week and misses a
bunch of events with alarms.  Perhaps there should be a setting like "expire
alarms older than 3 days."  In addition, multiple missed alarms should ideally
show in one window so that the user can review and dismiss them at once.

Comment 1

[Joey Minta]

Reporter:
   This seems like it might just be another way of creating bug 229916.  Can you
take a look at that bug and see if you agree?  If so, please resolve this bug as
a  duplicate of that one.

Comment 2

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

The alarm service is also entirely different on the trunk (and just aborning
this week, in fact).  I look forward to your code review and testing of that
code, though!

Comment 3

[Joey Minta]

No response from reporter.  Resolving duplicate.  (see comment #2)

*** This bug has been marked as a duplicate of 229916 ***