69858 - Motion JPEG network cameras cause memory leakage

Status: VERIFIED DUPLICATE of bug 69857

(SeaMonkey :: General, defect)

Description

[Brian Poole]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.0 i686; en-US; 0.8) Gecko/20010222
BuildID:    2001022208

I noticed this on Axis Network cameras' generated webpages, which the
payneconsulting URL is an example of. Search for 'mjpg' on google for other
sites that are open to the public if the payne is full or slow. Basically when
you are viewing the 320x240 motion jpeg mozilla will steadily consumes memory,
eventually causing it to use swap and starve everything else of memory. I'm
pretty sure the effect is the same for the other size 640x480, but that is not
tested. I had a running Mozilla with a mjpg from my own camera (on 10mbit
ethernet) going and when I came back from lunch the mozilla process was using
339M of memory (only limited by the fact that I only have 128M of RAM & 256M of
swap!). Memory is not consumed as rapidly when watching a camera via the
Internet, due to the slower updates I believe, but it is still occuring. There
is javascript in the HTML, so was not sure if this is JS, ImageLib, or what?

This occurs both in the 2001022208 and in the older Mozilla I was using,
20010213. Have not tested it on Windows, only Linux. Will test when I get home.
Netscape 4.76 on Linux does not do this so I believe this is a bug and not just
'what mjpgs do'.

Reproducible: Always
Steps to Reproduce:
1. Load http://www.payneconsulting.com/webcam/ (or an equivalent Axis network
camera served page)
2. Wait, memory will steadily be used, though the amount seems to depend on your
network connectivity. Fast connection -> faster memory usage. You should see
memory usage rise.

Actual Results:  6182 raj 16 0 38968 38M 12756 R 0.0 30.9 2:34 mozilla-bin

This is after 20 minutes of watching the mjpg. Started at around 20M of memory
usage and crept up steadily. As mentioned before, on a faster network connection
I can reproduce this much more quickly, steadily using around 100-160k of memory
in 3-4 seconds. This does not stop at any apparent point and consumes all memory
on the machine.

Expected Results:  Should have not used all of my bloody memory ;)

Well, don't know if it is 'critical' if no one else runs into it (how often are
mjpgs used?) but it is leaking memory and thats what the description of critical
says. G'luck.

Comment 1

[Andreas M. "Clarence" Schneider]

*** This bug has been marked as a duplicate of 69857 ***

Comment 2

[Stephen Walker]

vrfy dup