Closed
Bug 1325825
Opened 8 years ago
Closed 8 years ago
Thunderbird on Ubuntu won't start - using 5.6GiB memory
Categories
(Thunderbird :: Untriaged, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: doratheexplorer, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: hang, testcase-wanted)
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Ubuntu Chromium/55.0.2883.87 Chrome/55.0.2883.87 Safari/537.36
Steps to reproduce:
Since December 23rd, 2016 Thunderbird will not start. Tried to start in safe mode - same issue.
Uninstalled Thunderbird, restarted then reinstalled, same issue. rolled back to build 38, restarted, same issue. Started system monitor, started Thunderbird - package using 5.6GiB memory for start-up. Started Thunderbird using Terminal - system hangs due to memory usage returns killed after 5 minutes. Upgraded to 16.10 to see if this made a difference - same issue.
Actual results:
System hangs for 5 minutes, process ends (killed) on own. Mo crash report.
Expected results:
Thunderbird should have opened to allow use.
Reporter | ||
Updated•8 years ago
|
OS: Unspecified → Linux
Hardware: Unspecified → x86_64
Comment 1•8 years ago
|
||
If you are using imap accounts, does it help to create a new profile?
see https://support.mozilla.org/en-US/kb/using-multiple-profiles
Reporter | ||
Comment 2•8 years ago
|
||
OK, I created a new profile and Thunderbird opened immediately using the new profile.
Comment 3•8 years ago
|
||
Tina,
With your old profile, can you try a nightly build from https://archive.mozilla.org/pub/thunderbird/nightly/latest-comm-central/thunderbird-54.0a1.en-US.linux-x86_64.tar.bz2 ?
Summary: Thunderbird won't start - using 5.6GiB memory → Thunderbird on Ubuntu won't start - using 5.6GiB memory
Comment 4•8 years ago
|
||
Tina deleted the profile, so we don't have a testcase for this
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(doratheexplorer)
Keywords: testcase-wanted
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•