Bug 844275 - Move the GfxInfoThread so that it is guaranteed to run to completion before compositor creation. r=Cwiiis
This commit is contained in:
@@ -5,7 +5,6 @@
|
||||
|
||||
package org.mozilla.gecko;
|
||||
|
||||
import org.mozilla.gecko.gfx.GfxInfoThread;
|
||||
import org.mozilla.gecko.mozglue.GeckoLoader;
|
||||
import org.mozilla.gecko.util.GeckoEventListener;
|
||||
|
||||
@@ -92,15 +91,6 @@ public class GeckoThread extends Thread implements GeckoEventListener {
|
||||
|
||||
@Override
|
||||
public void run() {
|
||||
// Here we start the GfxInfo thread, which will query OpenGL
|
||||
// system information for Gecko. This must be done early enough that the data will be
|
||||
// ready by the time it's needed to initialize the LayerManager (it takes about 100 ms
|
||||
// to obtain). Doing it here seems to have no negative effect on startup time. See bug 766251.
|
||||
// Starting the GfxInfoThread here from the GeckoThread, ensures that
|
||||
// the Gecko thread is started first, adding some determinism there.
|
||||
GeckoAppShell.sGfxInfoThread = new GfxInfoThread();
|
||||
GeckoAppShell.sGfxInfoThread.start();
|
||||
|
||||
String path = initGeckoEnvironment();
|
||||
|
||||
Log.w(LOGTAG, "zerdatime " + SystemClock.uptimeMillis() + " - runGecko");
|
||||
|
||||
Reference in New Issue
Block a user