222911 - Mozilla exits after 4 s visiting www.mozilla.org/ without any user action

Status: RESOLVED EXPIRED

(Firefox Build System :: General, defect)

Description

[Helmut Schellong]

User-Agent:       Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5b) Gecko/20030915
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.5) Gecko/20030915

I have compiled the source rv:1.5, because there is no pkg.

104]  /usr/moz15/bin/mozilla &
[1] 19731
105]  Type Manifest File: /usr/moz15/lib/mozilla-1.5/components/xpti.dat
+++ JavaScript debugging hooks installed.
nsNativeComponentLoader: autoregistering begins.
nsNativeComponentLoader: autoregistering succeeded
nNCL: registering deferred (0)
GFX: dpi=87 t2p=0.0588235 p2t=17 depth=24
WEBSHELL+ = 1
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsChromeRegistry.cpp,
line 3189
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsChromeRegistry.cpp,
line 3189
WEBSHELL+ = 2
Note: verifyreflow is disabled
Note: styleverifytree is disabled
Note: frameverifytree is disabled
WEBSHELL+ = 3
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
Document file:///u/hp/2/de/ loaded successfully
***   Visiting by m-Button ***
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
WARNING: empty damage rect: update caller to avoid fcn call overhead, file
nsFrame.cpp, line 2551
*** 4 seconds later ***
[1]    Exit 11                       /usr/moz15/bin/mozilla
105]

Reproducible: Always

Steps to Reproduce:
1. visit mozilla.org
2. --
3. --

Actual Results:  
Mozilla exits

Expected Results:  
Mozilla exits not

Comment 1

[Helmut Schellong]

The same event with:
http://www.pronix.de/C/standard_C/c_programmierung_9.shtml#6
2..3 seconds -- exit

Comment 2

[Helmut Schellong]

Mozilla hangs:
http://www.pronix.de/C/standard_C/c_programmierung_16.shtml
kill mozilla-bin

Comment 3

[Helmut Schellong]

Compiled:

./configure \
 --prefix=/usr/moz15 \
 --enable-optimize=-O1 \
 --enable-strip \
 --disable-pedantic \
 --enable-crypto \
 2>&1 | tee Conf.out

Comment 4

[Helmut Schellong]

Now I have compiled with gcc3.3 (not with std 2.92.3),
and these exit problems not further exist.
Uff, uff, uff.
Unintended email notifications are away too.
Uff.

Comment 5

[Helmut Schellong]

New: I have compiled with gcc3.3.2 too.

Summary:
--------
Compiled in exactly the same way:
With gcc2.92.3:
     Exit and hang problems
With gcc3.3:
     OK! Very fine Mozilla.
With gcc3.3.2:
     The Subject/Sender-Window of all mail+news-folders is empty.
     There is an error message: "...wooa!..."
I cannot understand this different behaviour, this
compiler sensitivity.

Comment 6

[Helmut Schellong]

Second try:
With gcc3.3.2, without debug-output and with -O2:
     Very OKAY Mozilla, FAST!

103]  /usr/moz15/bin/mozilla &
[1] 36935
104]  l /usr/moz15
lrwxr-xr-x  1 root  wheel  14 Oct 24 09:05 /usr/moz15 -> /usr/moz15_332
105]

Comment 7

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 8

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.