Closed
Bug 674960
Opened 14 years ago
Closed 13 years ago
Thunderbird leaking memory only when Lightning (with Zimbra backend)
Categories
(Calendar :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: shobhitgupta12, Unassigned)
Details
(Keywords: memory-leak, perf)
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Build ID: 20110615151330
Steps to reproduce:
I am a Thunderbird user who uses Lightning with Zimbra Calender as my backend.
Actual results:
One of the major issues I am facing is that over time (throughout entire day), the memory consumption of Thunderbird starts to grow and goes as high as 1.3 GB by the next day. Then I restart my Thunderbird to make it use less memory.
I disabled all other addons, the problem disappeared. Next day I turned on only Lightning among my addons, and the issue reappeared.
I can conclude that Lightning is having some memory leak.
I know this bug description is quite vague. Can some tell me how can I help debugging this issue? What data can I collect?
Is there a way I could upload some kind of logs which might give some insight to everyone what is going wrong?
Expected results:
Thunderbird (with Lightning) shouldn't grow its memory consumption over time.
Reporter | ||
Updated•14 years ago
|
OS: Other → Windows Server 2008
I'm having this exact same problem. Continual memory leak with Thunderbird 6.0.2, Lightning 1.0b5. However, I'm using Google Apps as a backend. If I disable Lightning, the issue goes away. Re-installing Lightning also didn't fix the problem.
Comment 3•13 years ago
|
||
mmecca, can you advise Shobhit and rosieman? (Bas seems to be gone)
Comment 4•13 years ago
|
||
Does this still occur with Lightning 1.4? Is the cache setting enabled on the calendar?
Updated•13 years ago
|
Whiteboard: [closeme 2012-06-01]
Resolved per whiteboard
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2012-06-01]
You need to log in
before you can comment on or make changes to this bug.
Description
•