Closed Bug 73356 Opened 24 years ago Closed 23 years ago

HTTP pipelining causes insane memory usage

Categories

(Core :: Networking: HTTP, defect)

Product:
Core
Component:
Networking: HTTP
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED INVALID
Milestone:
mozilla1.0

People

(Reporter: m.mozilla-bugs, Assigned: darin.moz)

References

(
URL
)

Details

(Keywords: memory-leak, perf)

If I enable HTTP pipelining, I see the image loading problem of bug 55714. But I also observe problems with memory usage and cpu utilization. With pipelining enabled, visiting www.tirerack.com will cause CPU to be pegged, and memory usage to grow to at least 60 MB (my guess is that it would keep growing if my system had more memory). I've seen the problem on other websites as well, but just finally had a chance to pin it down to the pipelining option today. I don't know how high a priority fixing this is, but I think it should be put in to the release notes so that people don't mistake this bug as a sign that Mozilla just requires huge amounts of memory.
Blocks: 61690
Keywords: mlk, perf
HTTP pipelining is broken and will require major work to clean it up. For this reason, HTTP pipelining is by default a disabled pref.
Target Milestone: --- → mozilla1.0
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
INVALID since the old (broken) pipelining code has been removed.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
verified invalid per darin's comment.
Status: RESOLVED → VERIFIED
QA Contact: tever → junruh
You need to log in before you can comment on or make changes to this bug.