Closed Bug 2006234 Opened 1 day ago Closed 6 hours ago

Fake server frequently complains about not being able to write to a closed socket

Categories

(MailNews Core :: General, defect)

defect

Tracking

(thunderbird148 fixed)

RESOLVED FIXED
148 Branch
Tracking Status
thunderbird148 --- fixed

People

(Reporter: darktrojan, Assigned: darktrojan)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

A lot of test logs now contain the line:

JavaScript error: resource://testing-common/mailnews/Maild.sys.mjs, line 515: TypeError: can't access property "write", this._output is null

It's true, I did null the output bug 1991586, and in most cases the server is just trying to respond to a quit or log-out command. There's no actual problem here, but it's an annoying distraction.

There's no real need for the immediate closure, and it prevents writing any remaining data to the
socket. One test depended on the behaviour, but only as a work-around for another problem.

Assignee: nobody → geoff
Status: NEW → ASSIGNED
Attachment #9533228 - Attachment description: Bug 2006234 - Remove the option immediately close a nsMailReader's transport. r=#thunderbird-reviewers → Bug 2006234 - Remove the option to immediately close a nsMailReader's transport. r=#thunderbird-reviewers
Target Milestone: --- → 148 Branch

Pushed by john@thunderbird.net:
https://hg.mozilla.org/comm-central/rev/ceccb4849121
Remove the option to immediately close a nsMailReader's transport. r=mkmelin,john.bieling

Status: ASSIGNED → RESOLVED
Closed: 6 hours ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: