flushWindowSurfaceColorBuffer 模拟器启动问题

[2014-09-09 14:42:16 - ListView1] ------------------------------
[2014-09-09 14:42:16 - ListView1] Android Launch!
[2014-09-09 14:42:16 - ListView1] adb is running normally.
[2014-09-09 14:42:16 - ListView1] Performing cn.ac.siat.listview1.ListView1Activity activity launch
[2014-09-09 14:42:16 - ListView1] Automatic Target Mode: launching new emulator with compatible AVD 'Android14'
[2014-09-09 14:42:16 - ListView1] Launching a new emulator with Virtual Device 'Android14'
[2014-09-09 14:42:27 - Emulator] emulator: warning: opening audio input failed
[2014-09-09 14:42:27 - Emulator] 
[2014-09-09 14:42:27 - Emulator] creating window 28 27 320 480
[2014-09-09 14:42:27 - ListView1] New emulator found: emulator-5554
[2014-09-09 14:42:27 - ListView1] Waiting for HOME ('android.process.acore') to be launched...
[2014-09-09 14:42:38 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0x4 not found
[2014-09-09 14:42:38 - Emulator] FB: closeColorBuffer cb handle 0x3 not found
[2014-09-09 14:42:42 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0x8 not found
[2014-09-09 14:42:42 - Emulator] FB: closeColorBuffer cb handle 0x7 not found
[2014-09-09 14:42:47 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0xc not found
[2014-09-09 14:42:47 - Emulator] FB: closeColorBuffer cb handle 0xb not found
[2014-09-09 14:42:52 - Emulator] FB::flushWindowSurfaceColorBuffer: window handle 0x10 not found

[2014-09-09 14:42:52 - Emulator] FB: closeColorBuffer cb handle 0xf not found

Try this with 'Use Host GPU' turned off in the emulator settings. I had the same error and that fixed it. –   Egg Jul 31 at 18:40
	why does that cause a problem? –   789  Aug 1 at 15:32
	I have no idea, haha –   Egg  Aug 1 at 17:13
	but is still works pretty slow... even though i installed intel haxam –   789  Aug 2 at 18:07

Here's the deal. Host GPU is only supported for AVD devices that are using API 15 or later. You also have to have Android SDK Tools 17 or later installed. Also Host GPU is experimental. All of this is in the emulation documentation: http://developer.android.com/tools/devices/emulator.html

Also your machine has to support OpenGL (most do) and you will get better results if your machine has a separate GPU even though it will work with integrated graphic chipsets as well.

If you cannot take advantage of Host GPU then use the Snapshot option instead to gain some performance boost. This will take a snapshot of the ram on the initial start of the emulated device and then reuse it on initial boot start ups of the device. (Snapshot and Host GPU are actually mutually exclusive even though the ADV allows you to check both.)

From：http://stackoverflow.com/questions/25000723/error-while-starting-emulator-emulator-fbflushwindowsurfacecolorbuffer-wind