Open
Bug 347660
Opened 18 years ago
Updated 3 years ago
nsBufferedOutputStream::WriteSegments doesn't handle the reader returning zero
Categories
(Core :: Networking, defect, P5)
Core
Networking
Tracking
()
NEW
People
(Reporter: Biesinger, Unassigned)
References
()
Details
(Whiteboard: [necko-backlog])
Per http://lxr.mozilla.org/seamonkey/source/xpcom/io/nsIOutputStream.idl#60, the reader for writeSegments is allowed to return success and zero bytes. But, the buffered output stream does not handle that, it looks like it would go into an infinite loop in that case. This is a quite relevant case since when used via writeFrom, this would hang at EOF (when the input stream would return zero).
|
||
Updated•8 years ago
|
Whiteboard: [necko-backlog]
|
||
Updated•8 years ago
|
Severity: critical → normal
|
||
Comment 1•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
|
|
||
Comment 2•7 years ago
|
||
Bulk change to priority: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: P1 → P3
|
||
Comment 3•3 years ago
|
||
Bulk-downgrade of unassigned, untouched DOM/Storage bug's priority.
If you have reason to believe, this is wrong, please write a comment and ni :jstutte.
Severity: normal → S4
Priority: P3 → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•