Closed
Bug 1023191
Opened 10 years ago
Closed 10 years ago
crashing frequently with high memory (~1GB)
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: javad, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, Whiteboard: [addon:gcontactsync])
User Agent: Mozilla/5.0 (Windows NT 5.1; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243
Steps to reproduce:
24.5.0 is crashing frequently or say withing 5-10 minutes,
first it hangs , becomes unstable , and task manager show consuming memory more than 1,000,000kb very high and than crashing
i have many many addons to identify, but have a feeling it could be gcontactsync
i downloaded 30.0 beta 5 or something yesterday (lastest) -- same results!!!
Expected results:
let me know if i need to give any additional files/ add something like log?
trial and error in all add ons could be a problem but can try or will try atleast disabling all addons
yes gcontact sync could be proble, as after disabling it, it is working for much longer time, still need some time to reconfirm
gcontctsync verison 0.4.0rc6
Comment 2•10 years ago
|
||
https://support.mozilla.org/en-US/kb/safe-mode is the easiest and recommended first step in diagnosing. Indeed if it crashes within 5-10 minutes it's a no brainer.
Severity: normal → critical
Component: Toolbars and Tabs → General
Flags: needinfo?(javad)
Keywords: crash
Summary: crashing frequently → crashing frequently with high memory (~1GB)
do i need to try safe mode now??
i have disable gcontctsync verison 0.4.0rc6
both 24.5.0 as well as 30 beta are working without problem now.
will try to check with gcontactsync peson also
Flags: needinfo?(javad)
Comment 4•10 years ago
|
||
If you've definitively identified gcontactsync then we have all the info we need, you don't need safe mode. (but you might want to try it anyway to see what it's like)
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
Whiteboard: [addon:gcontactsync]
You need to log in
before you can comment on or make changes to this bug.
Description
•