790179 - Seamonkey exits when cmd console is closed after using 'start'

Status: RESOLVED DUPLICATE of bug 787313

(Core :: General, defect)

Description

[Lowell Anderson]

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120826 Firefox/15.0 SeaMonkey/2.12
Build ID: 20120826214753

Steps to reproduce:

Seamonkey behaves in two different ways depending on whether it is running or not:

Case 1. Seamonkey not running--From an XP cmd console enter:
               start https://bugzilla.mozilla.org/

Case 2. Seamonkey running--From an XP cmd console enter:
               start https://bugzilla.mozilla.org/



Actual results:

Case 1.  Seamonkey not running:
            a. The system starts Seamonkey
            b. Seamonkey displays the page:  https://bugzilla.mozilla.org/
            c. The cmd console remains open, as expected
            d. Exiting the cmd console causes Seamonkey to terminate.

Case 2. Seamonkey running:
            a. - c. identical to Case 1
            d. Exiting the cmd console does not cause Seamonkey to exit and the
                 page https://bugzilla.mozilla.org/ is still good to go.
           



Expected results:

In Case 1, Seamonkey should not terminate when the cmd console window is closed.

The above seems to be caused by recent changes to Seamonkey because earlier versions did not cause it to exit when the cmd console window was closed.

This is not a problem with  Internet Explorer or Firefox.

Comment 1

[Matthias Versen [:Matti]]

The difference is easy to explain
in case 1 the process is launched from this console as child process.

case 2 is the same except that the starting process detects an already running instance of the process. It then sends the URL that should be opened to the already running process and itself exists afterwards. The child process is therefore already gone and can't be killed by closing the commandline.

This is exactly the same with Firefox15.0.1, see also bug 790050
I will try to do a regression range search if my time permits it.

Comment 2

[Matthias Versen [:Matti]]

In the affected builds you get continuous debug output on the console if the gecko profile addon is running
MOZ_EVENT_TRACE sample 1347369907530 522

Last good:
2012-04-29
Built from http://hg.mozilla.org/mozilla-central/rev/8f377102841b

first bad:
2012-04-30
Built from http://hg.mozilla.org/mozilla-central/rev/cfaf90b22fc3

http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8f377102841b&tochange=cfaf90b22fc3

Comment 3

[Matthias Versen [:Matti]]

good
2012-04-28
Built from http://hg.mozilla.org/integration/mozilla-inbound/rev/cb240b2a69db

bad
2012-ß4-29
Built from http://hg.mozilla.org/integration/mozilla-inbound/rev/7ec73828b931

http://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=cb240b2a69db&tochange=7ec73828b931

Alexandre Poirot — Bug 673383 - Output stdout in regular command line on Windows. r=ted 

dupe of bug 787313