Thunderbird Freeze due to Calendar Entry - RRULE:FREQ=YEARLY;COUNT=62989201
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
People
(Reporter: miho_public, Unassigned)
Details
(Keywords: testcase, triaged)
Attachments
(1 file)
2.53 KB,
text/calendar
|
Details |
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:120.0) Gecko/20100101 Firefox/120.0
Steps to reproduce:
Start with a fresh profile. Open the attached *.ical file -> open -> Calendar.
The bug actually appeared to me with a Nextcloud calendar synchronized in Thunderbird. I narrowed the problem down to a single specific VEVENT contained in this file. This file is actually generated by Nextcloud and I removed all Events not causing the bug.
This is the VEVENT, copy and pasted from the file attached:
BEGIN:VEVENT
DTSTAMP:20240102T095244Z
UID:e5c1f980-b483-4b9a-ac3c-8182c17c80d2
SEQUENCE:2
SUMMARY:TÜV Octavia vereinbaren
DTSTART;TZID=Europe/Berlin:20220101T140000
DTEND;TZID=Europe/Berlin:20220101T150000
RRULE:FREQ=YEARLY;COUNT=62989201;INTERVAL=2;BYMONTH=1
CLASS:PUBLIC
STATUS:CONFIRMED
CREATED:20200121T205432Z
EXDATE;TZID=Europe/Berlin:20240101T140000
LAST-MODIFIED:20240102T095244Z
BEGIN:VALARM
TRIGGER:PT0S
ACTION:DISPLAY
DESCRIPTION:TÜV Octavia vereinbaren
END:VALARM
END:VEVENT
Actual results:
Thunderbird freezes completely. No error message is shown. Ubuntu's dialogue where I can either kill the Application or wait appears. Waiting does not unfreeze Thunderbird for 15 Minutes. When Thunderbird is reopened it will freeze again immediately. Thunderbird can be revived by deleting the config folder ($HOME/.thunderbird) and starting from scratch.
Expected results:
Calendar shows or error message is created. Thunderbird should not freeze completely.
Comment 1•1 year ago
|
||
Confirmed. Just opening the file will freeze Thunderbird. (Beware, will mess up profile, as you it's also freezing after restart so not easy to get it out, short of removing the file from the file system.)
Comment 2•1 year ago
•
|
||
I'll assume `RRULE:FREQ=YEARLY;COUNT=62989201´ is the problem. Who wants 63M occurrences...
Description
•