541196 - when talos or unittests 'quit' fennec, we still have process running with fast start

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

we need to figure out a way with our scripts or other tools to detect that we have 'shut down' the browser when we have fast start enabled.  Right now if fast start is enabled, we close down the browser, but the display is just shut off.  If we terminate the process, then we have an extra 30-45 seconds startup time.  Multiply that by a few hundred starts of the browser and our unittesting is very long.

Comment 1

[Brian Crowder]

Use the same shutdown mechanism Alex implemented for the installer?

Comment 2

[Brian Crowder]

Sorry, I misread this.  We just need to look for the hidden window somehow.  A simple tool could be written to do this.

Comment 3

[Aki Sasaki (not active)]

I'm going to guess this is why Ts is breaking, with a "shutdown script" window open:

sending: push /tests/talos/profile\/bookmarkbackups/CVS\Root
DEBUG: created profile
Failed ts: 
		Stopped Thu, 21 Jan 2010 13:58:36
FAIL: Busted: ts
FAIL: failed to initialize browser

Comment 4

[Joel Maher ( :jmaher ) (UTC -8)]

Talos should work without this bug, but it will be a lot slower.  Aki, lets figure out what is going on with your stuff.  I am working on a few new clean patches that are almost ready.

Comment 5

[Joel Maher ( :jmaher ) (UTC -8)]

I haven't seen this for a while.  Aki, can you confirm that this is still an issue?

Comment 6

[Aki Sasaki (not active)]

There have been a bunch of green runs since then, so I'm going to guess that this was either fixed or is sporadic.

Comment 7

[Doug Turner (:dougt)]

This year we mothballed windows mobile development.  See:

  http://blog.pavlov.net/2010/03/22/stopping-development-for-windows-mobile/

Marking bugs in the windows mobile / windows ce bucket as WONTFIX.