240166 - Hangs while starting with Error: No running window found

Status: RESOLVED EXPIRED

(Core Graveyard :: X-remote, defect)

Description

[Jim Brown]

User-Agent:       Mozilla/5.0 (X11; U; OSF1 alpha; en-US; rv:1.7b) Gecko/20040406
Build Identifier: Mozilla/5.0 (X11; U; OSF1 alpha; en-US; rv:1.7b) Gecko/20040408

Trunk builds for both 20040408 and 20040410 hang while starting the browser
after printing the message 'Error: No running window found.'.  The browser
display is set to another host (e.g. DISPLAY=lime:0).

The last working trunk build is 20040406.

Other bug reports for this message don't seem applicable.


Reproducible: Always
Steps to Reproduce:
1. Build from trunk for 20040408 or 20040410
2. mozilla DISPLAY is another host (e.g. DISPLAY=lime:0)
3. Try to start mozilla

Comment 1

[Boris Zbarsky [:bzbarsky]]

Sounds like a regression from bug 237283 

Comment 2

[Christopher Blizzard (:blizzard)]

This was probably fixed when 240174 was fixed.

Comment 3

[Jim Brown]

The message is gone but mozilla still fails to open a browser window (20040415
build).  mozilla-bin is idle (not cpu bound).

OSF1, DEC

Comment 4

[Christopher Blizzard (:blizzard)]

Hmm, interesting.  Is there another browser running on that display?

Comment 5

[Jim Brown]

No, there are no other browsers running on this display.
I have a number of xterm sessions but no browsers.

Comment 6

[Christopher Blizzard (:blizzard)]

If you set this before starting up:

NSPR_LOG_MODULES=XRemoteClient:5

what output does it give?  (The last few lines should be enough.)

Comment 7

[Jim Brown]

There is no output when I say 'setenv NSPR_LOG_MODULES XRemoteClient:5' and run
mozilla.  mozilla starts up and just hangs without opening a window.  I also
tried 'setenv NSPR_LOG_FILE N.log' and it just made an empty file.

Comment 8

[Andrew Schultz]

Jim: can you grab a stacktrace frmo the hang?

Comment 9

[Jim Brown]

Attachment: Stack/thread trace while hung

I interrupted it a few more times and thread 3 was gone but the others were
still there.  Thread 1 had the same traceback.

Comment 10

[Christopher Blizzard (:blizzard)]

If you let it sit there for 10 seconds, does it eventually time out?

Comment 11

[Jim Brown]

I think the answer is no.  I let it sit for several minutes to see if anything 
interesting would happen and nothing ever did.

Comment 12

[Christopher Blizzard (:blizzard)]

THis is all very strange.  There should be a 10 second timeout.

Comment 13

[Jim Brown]

The message 'Error: No running window found.' is no longer displayed but the
browser still hangs and never opens a browser window.

Comment 14

[Asa Dotzler [:asa]]

Is anyone else besides Jim seeing this? Is it a general *nix problem or just OSF/1?

Comment 15

[Jim Brown]

Here is the output from --enable-debug for a 20040519 trunk build.
Does this help any?

GFX: dpi=95 t2p=0.0666667 p2t=15 depth=8
++WEBSHELL == 1
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed, file nsWebShellWindow.cpp,
line 327
###!!! ASSERTION: HiddenWindow not created: 'NS_SUCCEEDED(rv)', file
nsAppShellService.cpp, line 515
Break: at file nsAppShellService.cpp, line 515
++WEBSHELL == 2
WARNING: NS_ENSURE_TRUE(factory) failed, file nsDocShell.cpp, line 6741
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(EnsureScriptEnvironment())) failed, file
nsWebShell.cpp, line 299
WARNING: NS_ENSURE_TRUE(factory) failed, file nsDocShell.cpp, line 6741
WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(EnsureScriptEnvironment())) failed, file
nsWebShell.cpp, line 290

Comment 16

[chris hofmann]

blizzard, are you still looking at this?  any chance for 1.7?

Comment 17

[Christopher Blizzard (:blizzard)]

I haven't been able to reproduce this.

Comment 18

[chris hofmann]

-minus for 1.7. renominate if someone comes up with an isolated test case where
we can make better progress.

Comment 19

[Andrew Schultz]

Jim: is this still a problem with a recent (trunk) build?

Comment 20

[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 21

[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.