88259 - Hang on startup screen when Memory Cache is disabled via size=0 or debug pref

Status: VERIFIED WORKSFORME

(Core :: Graphics: ImageLib, defect)

Description

[doctor__j]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.1+) Gecko/20010628
BuildID:    2001062806

Reproducible: Always
Steps to Reproduce:
1. Open Pref menu
2. Go to "Debug -> Networking" panel
3. Disable Memory Cache
4. Exit Mozilla
5. Start up Mozilla

Actual Results:  Hang on the startup screen.

Expected Results:  Mozilla can be started up as usual.

The bug doesn't happen on Win32 build 2001062706.

Comment 1

[Doug Turner (:dougt)]

john, can you look at this?

Comment 2

[John Taylor]

I am not getting this on windows or linux with recent builds. Marking WORKSFORME
for now. Dr. J, are you still seeing this? If so, please reopen. It could be
that because imgCache.cpp is giving a warning when no cache is available, and
that slows it down.

Comment 3

[doctor__j]

Well...
I can still reproduce the bug using Win32 nightly build 2001070609.
I'm on Win98SE.

Then "Hang" I mentioned is not "system becoming totally irresponsive".  What I
mean is that I can do other things as usual and Moz just stays at the startup
screen (Mozilla-throwing-flame picture) and browser still not launched.
Reopening bug...

Comment 4

[Tom Everingham]

John, I can confirm what doctor_j is seeing.   I used a win 98 box with the
071009 trunk build.  With mem-cache disabled NS6 gets stuck in the splash screen.  

Comment 5

[Tom Everingham]

I can also reproduce this on win NT 4 using last nights mozilla build, and the
0711 trunk. The only way I've found to get around the hang is to delete your
profile.

Comment 6

[John Taylor]

Pavlov - I think this may be imglib. imgRequest::OnStartDecode is calling
nsCacheEntryDescriptor::SetDataSize on a non-existant memory cache (since the
memory cache is disabled via the Debug->Networking pref), which seems to be
causing the hang.

Comment 7

[Ben Ruppel]

Note: you can get the same results by setting memory cache to 0 in the advanced
> cache prefs menuitem.  Since this bug is for a debug option that will probably
not be around for long, perhaps it should also cover this problem.

Comment 8

[hirata masakazu]

This is hurting recent Mac builds, too. After setting mem cache=0, loading a new
page or launching Mozilla hangs.
You need to delete the cache settings from prefs.js to make Mozilla back to work.
This is pretty serious, since there seems other problems that need mem cache to
be set zero for workaround. (See bug 92542 for ex.)
Marking All/All and adding hang kw.
2001072508 trunk for MacOS9.1

Comment 9

[Stephen Walker]

*** Bug 95069 has been marked as a duplicate of this bug. ***

Comment 10

[benc]

Can someone tell me what the "disable" flag in the original problem does to
prefs.js? Does it set the mem cache value to zero or do something else?

Comment 11

[R.K.Aa.]

*** Bug 98324 has been marked as a duplicate of this bug. ***

Comment 12

[Boris Zbarsky [:bzbarsky]]

It sets:

user_pref("browser.cache.memory.enable", false);

Comment 13

[Christopher Aillon (sabbatical, not receiving bugmail)]

I just fell prey to this on linux trunk 2001091621.  It hangs completely for me
and I have to `kill' the main mozilla thread and manually edit prefs.js if I
want to use Moz again.

Comment 14

[Damir Koscicaric]

problem remains in 0.9.4 :((((

Comment 15

[Terri Preston]

Reporter, could you try getting a newer build?  This wfm win 98 2001103103,
please reopen if this is still occuring

Comment 16

[Xuân Baldauf]

I can verify that this bug is fixed in build 2001103103 on Win98SE.

Comment 17

[benc]

V/fixed.
The mem.cache prefs behave quite differently these days...