I am running the IPC fuzzer in headless mode at DigitalOcean and this assertion failure blocks me from moving on. I do not know exactly what it is or how to work around it. The command for launching is: COMMAND="xvfb-run -e /dev/stdout $FIREFOX -P $PROFILE -no-remote $1 -height 300 -width 300" libGL error: No matching fbConfigs or visuals found libGL error: failed to load driver: swrast [29610] WARNING: NSPR_LOG_MODULES is deprecated. Please use MOZ_LOG instead.: file /srv/jenkins/jobs/faulty/workspace/xpcom/base/Logging.cpp, line 185 [29610] WARNING: dependent window created without a parent: file /srv/jenkins/jobs/faulty/workspace/toolkit/components/startup/nsAppStartup.cpp, line 665 ++DOCSHELL 0x61a000100280 == 1 [pid = 29610] [id = 1] ++DOMWINDOW == 1 (0x61900063ba80) [pid = 29610] [serial = 1] [outer = (nil)] ++DOMWINDOW == 2 (0x619000694b80) [pid = 29610] [serial = 2] [outer = 0x61900063ba80] [Faulty] Invalid process type for pid=29610 [Faulty] Initializing. [Faulty] Fuzz probability = 50000 [Faulty] Random seed = 4151131636 [Faulty] Strategy: pickle = enabled [Faulty] Strategy: pipe = disabled [time: 1930156516][29610->29610] [PBackgroundChild] Sending PBackground::Msg_PServiceWorkerManagerConstructor [time: 1930156861][29610<-29610] [PBackgroundParent] Received PBackground::Msg_PServiceWorkerManagerConstructor [29610] WARNING: GLX_swap_control unsupported, ASAP mode may still block on buffer swaps.: file /srv/jenkins/jobs/faulty/workspace/gfx/gl/GLContextProviderGLX.cpp, line 272 [29610] WARNING: SGI_video_sync unsupported. Falling back to software vsync.: file /srv/jenkins/jobs/faulty/workspace/gfx/thebes/gfxPlatformGtk.cpp, line 890 [29610] WARNING: OpenGL-accelerated layers are not supported on this system: file /srv/jenkins/jobs/faulty/workspace/gfx/thebes/gfxPlatform.cpp, line 2392 [time: 1931233570][29610->29610] [PCompositorBridgeChild] Sending PCompositorBridge::Msg_PLayerTransactionConstructor [time: 1931233859][29610<-29610] [PCompositorBridgeParent] Received PCompositorBridge::Msg_PLayerTransactionConstructor [time: 1931234341][29610->29610] [PCompositorBridgeParent] Sending reply PCompositorBridge::Reply_PLayerTransactionConstructor [time: 1931234442][29610<-29610] [PCompositorBridgeChild] Received reply PCompositorBridge::Reply_PLayerTransactionConstructor [time: 1931236464][29610->29610] [PLayerTransactionChild] Sending PLayerTransaction::Msg_PLayerConstructor [time: 1931236714][29610<-29610] [PLayerTransactionParent] Received PLayerTransaction::Msg_PLayerConstructor [time: 1931237166][29610->29610] [PLayerTransactionChild] Sending PLayerTransaction::Msg_PLayerConstructor [time: 1931237674][29610<-29610] [PLayerTransactionParent] Received PLayerTransaction::Msg_PLayerConstructor [time: 1931238269][29610->29610] [PLayerTransactionChild] Sending PLayerTransaction::Msg_PCompositableConstructor [time: 1931238447][29610<-29610] [PLayerTransactionParent] Received PLayerTransaction::Msg_PCompositableConstructor [time: 1931239254][29610->29610] [PCompositorBridgeChild] Sending PCompositorBridge::Msg_PTextureConstructor [time: 1931239462][29610<-29610] [PCompositorBridgeParent] Received PCompositorBridge::Msg_PTextureConstructor [time: 1931248873][29610->29610] [PLayerTransactionChild] Sending PLayerTransaction::Msg_Update [time: 1931249142][29610<-29610] [PLayerTransactionParent] Received PLayerTransaction::Msg_Update [time: 1931250040][29610->29610] [PLayerTransactionParent] Sending reply PLayerTransaction::Reply_Update [time: 1931250162][29610<-29610] [PLayerTransactionChild] Received reply PLayerTransaction::Reply_Update [time: 1931262217][29610->29610] [PCompositorBridgeChild] Sending PCompositorBridge::Msg_PTextureConstructor [time: 1931262588][29610<-29610] [PCompositorBridgeParent] Received PCompositorBridge::Msg_PTextureConstructor [time: 1931265651][29610->29610] [PLayerTransactionChild] Sending PLayerTransaction::Msg_Update [time: 1931265868][29610<-29610] [PLayerTransactionParent] Received PLayerTransaction::Msg_Update [time: 1931266307][29610->29610] [PLayerTransactionParent] Sending reply PLayerTransaction::Reply_Update [time: 1931266448][29610<-29610] [PLayerTransactionChild] Received reply PLayerTransaction::Reply_Update [time: 1931273125][29610->29610] [PCompositorBridgeChild] Sending PCompositorBridge::Msg_NotifyRegionInvalidated [time: 1931273398][29610<-29610] [PCompositorBridgeParent] Received PCompositorBridge::Msg_NotifyRegionInvalidated [time: 1931277029][29610->29610] [PVRManagerParent] Sending PVRManager::Msg_NotifyVSync [29610] WARNING: Unsupported XShm Image format!: file /srv/jenkins/jobs/faulty/workspace/widget/nsShmImage.cpp, line 185 [GFX2-]: Failed to lock WindowSurface, falling back to XPutImage backend. Assertion failure: mFormat != gfx::SurfaceFormat::UNKNOWN (Could not find SurfaceFormat for visual!), at /srv/jenkins/jobs/faulty/workspace/widget/gtk/WindowSurfaceX11.cpp:25

Christoph, are you running nightly/local build? Does turning off hardware acceleration help?

IIRC, Andrew Comminos had previously mentioned that with XVFB you might need to force it to use a 24 bit pixel depth in the command-line arguments in this situation.

What Lee said. Try adding -s "-screen 0 1024x768x24" to your xvfb-run arguments.

It's a local build with: https://github.com/posidron/mozilla-build-configs/blob/master/mozconfig.fuzzing.common https://github.com/posidron/mozilla-build-configs/blob/master/mozconfig.mi-asan-ipc-fuzzer as MOZCONFIGs. I just tried your suggestion and added: user_pref("layers.acceleration.disabled", true); but it had no effect.

That did it. Thanks Lee and Kartikaya. Yea, I recall that as well for another issue but always ended up in "xvfb-run: error: Xvfb failed to start". Thanks, I will mark this as resolved.

(In reply to Milan Sreckovic [:milan] from comment #6) > Created attachment 8795854 [details] > Bug 1301357: Diagnostic patch only. Check what depth/mask we are dealing > with in case we fail. > > Review commit: https://reviewboard.mozilla.org/r/81816/diff/#index_header > See other reviews: https://reviewboard.mozilla.org/r/81816/ Not sure if it's worth adding more information to that note, and if this is the right information to add, but there's the patch.

Comment on attachment 8795854 [details] Bug 1301357: Diagnostic patch only. Check what depth/mask we are dealing with in case we fail. https://reviewboard.mozilla.org/r/81816/#review80418 This is the wrong place to deal with this. The diagnostic info shold go in the WindowSurfaceX11 constructor which does the assert.