Closed Bug 1498798 Opened 7 years ago Closed 7 years ago

Activating lightning slows down thunderbird to being unusable

Categories

(Calendar :: General, defect)

Lightning 6.2.2.1
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mnl, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:62.0) Gecko/20100101 Firefox/62.0 Steps to reproduce: Thunderbird 60.2.1/Lightning 6.2.2.1 (not in the list) After upgrading Thunderbird to 60.0/Lightning ?, thunderbird became terribly slow. Further upgrading to the latest versions (see above) didn't fix things. Actual results: When lightning is activated, in thunderbird is slowed down. Literally everything: checking for mails, retrieving mails, writing mails (typing). (Only lightning works normally.) Lightning is the only active add-on. When deactived, everything works fine. Expected results: No slow down.
Just found a "workaround" by chance: When I disable (uncheck) all calenders after (a looooong) startup, the "mail part" works normally again. I can even reactivate all the calendars and it keeps working normally!
The "workaround" only lasts until the next calendar synchronization. No matter whether the synchronization happens automatically or is triggered manually, it causes the slow behavior to reoccur. Repeating the uncheck/reactivate cycles for the calendars "fixes" it again.
It appears that the problem was caused by the selection of "All Events" in the drop-down menu. I don't know if I changed this by accident or if the change was caused by an update. However, selecting "Events in the Next 14 Days" restores normal behavior.
Resolving as per comment 3.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME

The issue still persists.

IMHO - The selection of "All Events" should not be an issue! If there is no fix then the All Events should be removed from the drop down. One can't expect ordinary users to accept that an option that is shown breaks the product.

You need to log in before you can comment on or make changes to this bug.