Closed Bug 63383 Opened 24 years ago Closed 23 years ago

WinME: Mozilla hangs @startup if system resources are "low"

Categories

(SeaMonkey :: UI Design, defect)

Product:
SeaMonkey
Component:
UI Design
Platform:
x86
Windows ME
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 53952

People

(Reporter: olaf, Assigned: law)

Details

sorry if this should be a dupe. I couldnt find a similiar bug.

When system resources are "low" i.e. less than 70%, Mozilla doesn't start.
This applies to NS6, too.
When running with the /console option it shows that Mozilla hangs after:
stdout directed to dynamic console
stderr directed to dynamic console

The only way (I know of) to fix this, is to reboot to free system resources.
Well Mozilla requires at least 32MB (from my own experience) to run. So if you 
have say 64MB and 70% is used, it sounds logical that it won't start...
Not a blocker imho.
Fabian.
well... I've got 128MB.
Anyway, I don't think this is a RAM-problem.
At the moment I've about 60MB free RAM, system resource is at 57%, user at 57% 
and GDI at 75% but Mozilla still wont start.
well does it ever start?
Sending to toolkit. Although this might be XPApps.

Do we have or could we build a debug build that could explain what is 
happening?
Assignee: asa → trudelle
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doronr → jrgm
it sure does start...right after I rebooted. Than in runs like a charm, but 
after starting (and closing) a couple of other programs, it just wont start.
I had this problem with various builds and also on win98.
My current build is 0.6 (milestone 18?) but the "final" of netscape has the 
same problem.
I don't see how this could possibly have anything to do with toolkit.  ->xpapps
Assignee: trudelle → vishy
Component: XP Toolkit/Widgets → XP Apps
QA Contact: jrgm → sairuh
olaf@groessenwahn.com
 can you please download a current nightly build and test this.  mozilla 0.6 and
Netscape 6 are getting quite old.  I have not experienced this problem on any
recent win32 build.
I just was able to start mozilla with system resources at 44%...
ok. I downloaded and installed the build dd. 21.12.
It is still the same. 60% system resources and it wont start.
But no problem starting ns 4.7, opera 5 or ie 5.5...
first, not a blocker.
could you try with a new profile (mozilla -profilemanager) and see if that
helps?  Are you perhaps running outlook 2k at the same time?
Severity: blocker → critical
ok. I am running with a new profile now (deleted all others and created a new 
one)
I am not running outlook. the only programs running when problem occurs are 
eudora, mirc and my seti-client. However, even if I quit all these programs and 
any other I may have running, the problem persists.
I've done some testing and it seams that if resources drop below 65% (system 
and user; gui doesn't seam to have an effect) mozilla won't start...
I also did a re-install of WinME without any improvement.
As for blocker or non-blocker... I would dump a browser if it doesn't always 
start (like the competitors do)...

have a happy new year
Marking NEW as per comments.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I am having a similar problem running the latest nightly 20010111.. on Windows 
NT.  Using the console mode here is what is output:

stdout directed to dynamic console
stderr directed to dynamic console
 I am inside the initialize
 Hey : You are in QFA Startup
(QFA)Talkback loaded Ok.

At which point Mozila hangs.

Some background.  This AM I was running an older nightly just fine (20001217.., 
I think).  I decided, based on comments, to grab a newer nightly.  I first tried 
the Installer version, and then the Talkback version, neither will load.  
Netscape 6 worked fine until I tried to run the current nghtly.

I am running on Windows NT 4.0 with Service Pack 6 (freshly installed yesterday, 
as were security updates to IE 5.5).  I have 256 MB RAM.

I uninstalled NS 6, and reinstalled NS 4.76, which works fine.

If you need more info get in touch with me at evers@battelle.org.
This could be a dupe of 56581 ?
I encountered this problem, too. And I'm using Windows ME, too. (But it is the 
Traditional Chinese version)
When I upgraded my PC's OS from Win98 to WinME, I've found that sometimes NS6 
(beta) didn't start. When I called Norton CrashGuard, and killed the process 
called "WIN95 RPC Wmsg Window", the splash screen of NS6 would then appeared, 
and NS6 could started as usual.

Now I've just installed Mozilla 0.7, and it wouldn't started as before. 
However, I cannot use the above method, since Norton CrashGuard is not for 
Windows ME system.

Could this ("WIN95 RPC Wmsg Window") help investigating the problem?
there's another bug for failing to start that relates to DDEML.  I suspect 
that's what you're seeing.
jrgm, who's testing stuff like this? i don't it's me at the moment. punt as
needed... ;)
QA Contact: sairuh → jrgm
from vishy, over to law for a look.

Please look at bug 56581, which mentions that mozilla will
work exactly once after a cold reboot, let's get that
datapoint before marking a dup.
Assignee: vishy → law
Summary: Mozilla fails to start if system resources are "low" → WinME: Mozilla hangs @startup if system resources are "low"
hi.  using 0.91 on winME, and i'm still having the problem described here.  
talkback doesn't even initialize for me when Mozilla is going to die either.  i 
crash the same place olaf does.  the latest case happened at 62.8 of 96MB free, 
just now.  but this has been a consistent problem.  i do not look forward to 
the prospect of rebooting before every time i dial into my ISP.

even if this doesn't get fixed anytime soon, could we of non-infinite RAM at 
least get an error message or something?
I've been running a similar thread #72876 since March.
I cannot seem to get Mozilla to start after my PC's been on for some time, or
when I have started Mozilla a couple of times (mostly about 4 to 5) and closed
it again.
It's not running in the background, it's taking up loads of memory and letting
only part of it go.
I'm now onto downloading and installing Moz20010525 and see what this build does.

Running a P3-450, 256Mb, WinME.
On a sidenote. If I do a reboot, everything works fine.
If I do a reboot and only let genome@home run for a couple of hours, then try to
start Mozilla, it won't, although Wintop is saying it is running in the
background, using a couple of threads and a load of memory. Never checked my
resources at the time, so I don't know there.

I hope it will be resolved soon. It's been going on for too long now!

I have closed my bug #72867 for the last build I tried worksforme :)

Been doing network games the whole weekend, and I didn't have any problems
getting Moz back online, even after playing games for 12 hours in a row. I
usually eneded up with more than 80% resources back, but even build 2001060104
worked with 50% resources. 

Yabadabadoo!!
Any current (recent) complaints of this still happening?  I think this is a dup 
of bug 53952.  Please re-open if it is not fixed.

*** This bug has been marked as a duplicate of 53952 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.