Closed Bug 805405 Opened 9 years ago Closed 7 years ago

Memory leak after LAN unplugged (Thunderbird 16.0.1, Lightning 1.8, Provider for Google Calendar 0.17)

Categories

(Calendar :: Provider: GData, defect)

Lightning 1.8
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: 0h, Unassigned)

Details

User Agent: Opera/9.80 (Windows NT 5.1; U; en-GB) Presto/2.10.289 Version/12.02

Steps to reproduce:

I'm running Thunderbird with "Events ant Task" panel opened. Several times I've noticed Thunderbird allocated about 800 MB of the memory (normal size for my system is around 200 MB) and everything hangs. It only happens if Provider for Google Calendar is enabled and I noticed it after last update. I have 9 calendars: 1 from Exchange (using DavMail), 7 from Google, and 1 from local file.

After some investigation I've got following procedure to reproduce the problem:
1. Run Thunderbird.
2. Wait list of events appear.
3. Unplug the LAN cable.
4. Wait until next update of the events list.


Actual results:

One of two processor cores starts to work on 100% and memory usage start growing. Reconnecting the LAN cable doesn't help.


Expected results:

Nothing / warning.
OS: All → Windows XP
Hardware: All → x86
I have the same issue with TB17b1 and Lightning 19b2 and Provider for google 0.18pre, on XP.
There has been a major rewrite of the Provider for Google Calendar between version 0.32 and 1.0. A vast number of bugs have been fixed during this rewrite, therefore I am closing lots of old bugs that I think might either be fixed or no longer apply to the latest version.

Please read the updated FAQ [1] for details on known issues. If you can reproduce your issue with the latest version of the Provider for Google Calendar and you can't find an existing bug that handles your case, please reopen this issue.

Thank you for your understanding.

[1] https://wiki.mozilla.org/Calendar:GDATA_Provider
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.