55072 - use of Proxy causes error in reported NT memory usage

Status: RESOLVED WORKSFORME

(SeaMonkey :: General, defect, P3)

Description

[Tony Tovar]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; m18) Gecko/20000929
BuildID:    2000092908

I have been running a stable NT4.SP6a workstation setup for several months.
Every week or so, I download the latest Mozilla Nightly.  Starting with (I
think) the 9-27-00 Nightly, the reported memory usage is incorrect.


Reproducible: Always
Steps to Reproduce:

What I am doing:
- before loading Mozilla, I load the NT Task Manager and note the current
overall memory usage
- I load the Mozilla Nightly
- Task Manager will report, typically, 16 MB usage by the "Mozilla" process
- I'll browse for about 30 minutes, opening and closing multiple windows in Mozilla



Actual Results:  Afterwards, Task Manager will report an overall increase of
memory usage of 30-40 MB but the "Mozilla" process will only be using 2 MB.  No
other applications have been accessed this whole time, so Mozilla must be
responsible for memory usage.
			

Expected Results:

Comment 1

[Tony Tovar]

UPDATE #1
When I started the process of reporting a new bug, the NT Task Manager was
reported only 2 MB of memory usage for the "Mozilla" process.  By the time I
finished (and had opened and closed some more windows), it was back to 30 MB,
which I believe is the correct usage to report.  I exited from the Mozilla
program, the last window disappeared, but the process remained open in Task
Manager (and was still holding onto 22 MB).  I tried to reload Mozilla but
received the error message, "The instruction at '0x0080206c' referenced memory
at '0xffffffff'. The memory could not be 'read'."  I clicked OK and saw that the
open "Mozilla" process finally closed.  I reloaded Mozilla again and everything
was fine.

UPDATE #2
All of these problems may be related to problems with the Proxy feature (see bug
51074).

I am running AdSubtract, an advert and cookie blocking utility which runs as a
local HTTP 1.0 proxy, port 4444.  I had configured Mozilla (on or about
9-21-00?) to use HTTP 1.0 as well as using the local (ie. same-machine) proxy.
I think it's only since then that I've been having problems.  The very next
Nightly that I installed, however, removed the Advanced Debug option for HTTP
mode so I don't know what it's currently using.

I am switching off the Proxy feature and I'll see what happens.

Comment 2

[Doron Rosenberg (IBM)]

so, if you do not use the proxy software, this goes away?

Comment 3

[Tony Tovar]

Yes, it appears that the memory problem *was* related to the Proxy function.  I
deleted my USERS50 folder (effectively resetting Mozilla to defaults), then
hammered on my 09-29-00 Nightly, opening and closing many windows; the reported
memory usage for the "mozilla" process worked consistently.

I also wonder if it could be related to the use of HTTP 1.0?  Before the current
Nightly removed the Debug menu, I changed the protocol settings to use HTTP 1.0
because my AdSubtract proxy software only supports 1.0.

Is there any way to select between HTTP 1.0 and HTTP 1.1 now?
I will also try re-enabling the Proxy service though I expect it to fail if
Mozilla is back to the default HTTP 1.1 setting.

Comment 4

[Asa Dotzler [:asa]]

the debug pref panel should still be available in the M18 nightly builds.  Avoid
the MN6 nightlies.

Comment 5

[Keyser Sose]

Reporter is this still a problem?

Comment 6

[Tony Tovar]

The 11-07-00 build seems to work very well (on NT4).  Opening and closing
multiple windows seems to create a predictable increase/decrease in memory usage.

Unfortunately, I still do not have the Debug screen, so I don't know how to
switch between HTTP 1.0 and 1.1.  (Remember, my local proxy s/w only supports
1.0 and I had previously set Mozilla for HTTP 1.0 in the Debug screen...)  I
know you said to use one Mozilla branch instead of the other, but I simply
downloaded the latest "talkback" .ZIP from
http://ftp.mozilla.org/pub/mozilla/nightly/latest

Which branch is that?

Comment 7

[Asa Dotzler [:asa]]

Tony Tovar, the latest directory is just that, whichever is latest.  Please
avoid that directory.  Instead use the /nightly directory and only get builds
from directories labeled MTrunk (avoid MN6 directories).  You know you got a
branch build of the debug menus and the buildID are missing.