Closed Bug 537905 Opened 16 years ago Closed 16 years ago

After TB3 crash IMAP connections not reset

Categories

(MailNews Core :: Networking: IMAP, defect)

Product:
MailNews Core
Component:
Networking: IMAP
Version:
1.9.1 Branch
Platform:
x86
Windows 7
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 537889

People

(Reporter: thomas.ohms, Unassigned)

Details

(Keywords: crash)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.6 GTB6 (.NET CLR 3.5.30729) FirePHP/0.3 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; de; rv:1.9.1.5) Gecko/20091204 Lightning/1.0b2pre Thunderbird/3.0 Issue: After TB3 has had a crash and one tries to restart TB doesn't reset active IMAP connections and so will not be able to connect anymore if limit of server is reached. In my case I restarted my IMAP server, but there should be another way doing this as most of users are not able to restart any kind of server. Side note: The crash itself seems to be an incompatibility between Funambol sync and latest German dictionary with hunspell support. But this should not have to do with the connections problem - as I had crashes before installing those addons and there was the same. Reproducible: Always Steps to Reproduce: 1. Do sth. that let's TB crash 2. Try to restart and connect to your IMAP 3. Possibly you need a couple of accounts on that server for reaching the limit. In my case I have by default 12 active connections and a server limit of 20 per IP. Expected Results: Reset old IMAP connections before reconnecting after crash.
Version: unspecified → 3.0
please list your crash report ids, preferably for crashes that don't have the extensions installed http://kb.mozillazine.org/Breakpad#Location_of_crash_reports
Severity: normal → critical
Component: General → Networking: IMAP
Keywords: crash
Product: Thunderbird → MailNews Core
QA Contact: general → networking.imap
Version: 3.0 → 1.9.1 Branch
well, you're always crashing at precisely the same address as bug 537889, that makes this bug a duplicate, sorry. disable the extension.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.