792602 - Thunderbird 15.01 with Lightning 1.7 locks up on Windows 7

Status: RESOLVED INCOMPLETE

(Calendar :: General, defect)

Description

[jgibbs]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20100101 Firefox/15.0.1
Build ID: 20120905151427

Steps to reproduce:

Sent an invite for an appointment.


Actual results:

On receipt of acceptance, TB locked up with high CPU utilization and became unresponsive.  Killing the TB process and restarting did not resolve the issue.  It would start up and be responsive for a couple of seconds and then freeze again.

Disabling lightning prevents the lockup.


Expected results:

TB should have accepted the invite and let me carry on with my day job.

Comment 1

[Stefan Sitter [:ssitter]]

What version of Thunderbird do you use? What version of Lightning do you use? What type of calendar provider do you use? Do you use additional calendar related extensions? Do you get any error messages in Tools > Error Console?

Comment 2

[jgibbs]

Title of the bug gave the versions:

TB 15.01
Lightning 1.7

No calendar provider, just the internal calendar system.

I opened up the calendar-data/local.sqlite file and removed the appointment that caused the lockups and the problem went away.  I have a copy of the original though for debug purposes.

This has happened one before to me, and both times the confirmation was received from an Novell Groupwise system.

There are errors in the log, but nothing that seems to be directly related to this problem.

Digging a little further, I've just tried restoring the bad calendar file and it didn't lock up until I foind the 'Accept' message.  As soon as I clicked on it, it freezes up again, so it seems to be related to the process of joining the accept to its appointment.

Comment 3

[jgibbs]

Attachment: Accept message source causing issue

This message causes TB to lockup when Lightning 1.7 is enabled and it is clicked on in the INBOX

Comment 4

[Markus Adrario [:Taraman]]

Running the ical code of the message in an Ical-Validator [1] shows an error in the recurrence rule:
RRULE:FREQ=YEARLY;BYDAY=255SU;BYMONTH=9

According to ical Spec [2] Page 42 this would mean:
every 255th Sunday of September

That is of course impossible
What was the recurrence rule supposed to be?

Anyway, Lightning should deal with such faulty ical-code.

[1]: http://icalvalid.cloudapp.net/
[2]: http://www.ietf.org/rfc/rfc2445.txt

Comment 5

[jgibbs]

I don't know what the original schedule was intended to be, as it wasn't created by me. It was an appointment received from a GroupWise mail system.

So I agree, TB should be coping with faulty incoming ical requests that are out of my control.

Comment 6

[Markus Adrario [:Taraman]]

Ok, looking at it again, I see that not the event has the recurrence, but it is from the timezone (The date of the changeover to winter-time.)

This would come from the creating Application.
For Timezone NZST it should read:
RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=9

Still: TB/Lightning shouldn't crash.

Comment 7

[Wayne Mery (:wsmwk)]

jgibbs, do you still see this issue?

Comment 8

[jgibbs]

I'm sorry but I couldn't tell you. I stopped importing those ical requests years ago because it rendered TB unusable.

Comment 9

[Philipp Kewisch [:Fallen][☁️📆]]

Thanks for getting back so quickly and for taking the time to report this. We'll file new bugs when we can pinpoint specific perf issues.