978060 - Freeze (hang) on event with invalid BYDAY rule part in DAILY recurrence rule

Status: NEW

(Calendar :: General, defect)

Description

[bt2gxtyejv]

Attachment: calendar3.ics

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20140212131424

Steps to reproduce:

may or may not be related to 
"Bug 377487 - Freeze (hang) on .ics file which has BYYEARDAY and BYDAY in an RRULE "
---

New Calendar-> Calendar on the network -> ICS -> calendar.ics:
>>>
BEGIN:VCALENDAR
BEGIN:VEVENT
UID:calendar.3558.field_time.0.21
SUMMARY:Stammtsich Wetzlar
DTSTAMP:20140228T105223Z
DTSTART:20140318T180000Z
DTEND:20140318T220000Z
RRULE:FREQ=DAILY;INTERVAL=1;BYDAY=+1TU,+3TU,+5TU;UNTIL=20141230T225959Z;COUNT=52;WKST=MO
URL;VALUE=URI:https://www.piratenpartei-hessen.de/content/stammtsich-wetzlar
END:VEVENT
END:VCALENDAR
<<<



Actual results:

Thunderbird 24.3.0 / Sunbird 1.0b1: crash / freeze


Expected results:

process VEVENT or drop it, if invalid.

Comment 1

[Stefan Sitter [:ssitter]]

I can confirm the hang (not the crash) using Lightning 3.1a2 (BuildID: 20140301004004). After opening the attached test case Thunderbird hangs in an endless loop using 100% of CPU cycles. Happens with both libical and icaljs backend.

There are several errors in the attached test case that should be reported back to the creator of the calendar to provide a calendar that conforms to the icalendar standard.

COUNT and UNTIL are mutually exclusive, they must not occur in the same RRULE.

The BYDAY rule part must not be specified with a numeric value when the FREQ rule part is not set to MONTHLY or YEARLY.

VERSION and PRODID property is required on all VCALENDAR components.

If you fix BYDAY=+1TU,+3TU,+5TU to something valid like BYDAY=TU the calendar can be loaded correctly.

Comment 2

[Wayne Mery (:wsmwk)]

Reproduces with 52.5.0 and calendar 4.9. Also subsequently hangs startup.

Do you consider this to be a duplicate?

Comment 3

[BugBot [:suhaib / :marco]]

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.