Closed
Bug 901307
Opened 12 years ago
Closed 10 years ago
Memory Leak in Lightning 1.9.1 with Exchange EWS Provider Add-on for Lightning
Categories
(Calendar :: Lightning Only, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: mad.engineer, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [addon:Exchange EWS Provider?])
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212
Steps to reproduce:
Installed Lightning 1.9.1 with TB 17.0.7, OS X 10.8.4, with Exchange 2007/2010 Calendar and Tasks Provider add-on to access my Exchange 2010 Calendar.
Actual results:
TB became very slow, checked Activity Monitor and noticed that TB was using upwards of 750MB memory
Expected results:
Un-installed Lightning add-on, TB went back to normal with memory usage around 150MB or so. There is definitely a memory leak in Lightning 1.9.1 making is unsable with TB 17.0.7
Reporter | ||
Updated•12 years ago
|
OS: All → Mac OS X
Hardware: All → x86
Comment 1•11 years ago
|
||
Is it better with Thunderbird 24 and updated Lightning?
Can you localize the problem to specific calendar items, like recurring appointment(s)?
Flags: needinfo?(mad.engineer)
Reporter | ||
Comment 2•11 years ago
|
||
Upon further use, it appear that the memory leak start when using the Exchange EWS Provider Add-on for Lightning: http://www.1st-setup.nl/wordpress/?page_id=133. Even with TB 24.0 and Lightning 2.6, as soon as you install and setup the calendar, the memory usage on TB jumps to ~800MB constantly making TB so slow that it becomes un-usable. As soon as you un-install the add-on, TB works OK.
Flags: needinfo?(mad.engineer)
Comment 3•11 years ago
|
||
(In reply to mad.engineer from comment #2)
> Upon further use, it appear that the memory leak start when using the
> Exchange EWS Provider Add-on for Lightning:
> http://www.1st-setup.nl/wordpress/?page_id=133. Even with TB 24.0 and
> Lightning 2.6, as soon as you install and setup the calendar, the memory
> usage on TB jumps to ~800MB constantly making TB so slow that it becomes
> un-usable. As soon as you un-install the add-on, TB works OK.
see https://www.1st-setup.nl/bugzilla/show_bug.cgi?id=279
does that newer version of the addon help?
Severity: normal → major
Flags: needinfo?(mad.engineer)
Summary: Memory Leak in Lightning 1.9.1 → Memory Leak in Lightning 1.9.1 with Exchange EWS Provider Add-on for Lightning
Reporter | ||
Comment 4•11 years ago
|
||
I've tested this with the latest/last version 3.2.0-Beta-46 that is out there with the same symptoms that is described in the above bug report. Unfortunately, Michel Verbraak have decided not to work on this add-on anymore so not sure who can fix this.
Flags: needinfo?(mad.engineer)
Comment 5•10 years ago
|
||
(In reply to mad.engineer from comment #4)
> I've tested this with the latest/last version 3.2.0-Beta-46 that is out
> there with the same symptoms that is described in the above bug report.
> Unfortunately, Michel Verbraak have decided not to work on this add-on
> anymore so not sure who can fix this.
They are up to beta 77 as of spring 2014.
Are you able to determine, using Help | Troubleshooting | About:memory whether the high memory usage is actually in EWS, vs Calendar?
Flags: needinfo?(mad.engineer)
Reporter | ||
Comment 6•10 years ago
|
||
sorry, I haven't had a chance to use this add-on beyond the last version that it's original author released.
Flags: needinfo?(mad.engineer)
Comment 7•10 years ago
|
||
Thanks for the feedback.
(In reply to mad.engineer from comment #6)
> sorry, I haven't had a chance to use this add-on beyond the last version
> that it's original author released.
I looks to me like EWS is at fault - in which case the bug will be closed INVALID. But we don't know yet, so closing INCOMPLETE. If you do further testing, please provide more information based on the questions above.
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [addon:Exchange EWS Provider?]
You need to log in
before you can comment on or make changes to this bug.
Description
•