Crash with dri and gbm ozone plugins

[azam]

hi,

This question may not be related to CEF but chromium. I wanted to test the dri and gbm ozone platform on my linux desktop without xserver.

I built the content_shell target in chromimum trunk and tried to run it as follows.

$ content_shell --disable-setuid-sandbox --ozone-platform=dri

the application crashed. Below is the crash logs. Any idea what I am doing wrong that causes the crash?

Thanks in advance.

root@root:~/275973-gbm-content-shell/chromium_trunk/chromium/src/out/Debug# ./content_shell --disable-setuid-sandbox --ozone-platform=dri
[6369:6369:0708/155213:73787072207:ERROR:browser_main_loop.cc(160)] Running without the SUID sandbox! See https://code.google.com/p/chromium/wiki ... evelopment for more information on developing with the sandbox on.
Home directory /root not ours.
[6369:6369:0708/155213:73787083612:INFO:audio_manager_pulse.cc(261)] Failed to connect to the context. Error: Connection refused
[6369:6369:0708/155213:73787125160:ERROR:window_tree_host_ozone.cc(55)] Not implemented reached in virtual void aura::WindowTreeHostOzone::Show()
[6369:6384:0708/155213:73787166121:WARNING:proxy_service.cc(904)] PAC support disabled because there is no system implementation
[6388:6388:0708/155213:73787129551:FATAL:surface_factory_ozone.cc(29)] Check failed: impl_. No SurfaceFactoryOzone implementation set.
#0 0x0000007c4903 base::debug::StackTrace::StackTrace()
#1 0x00000070807f logging::LogMessage::~LogMessage()
#2 0x0000016501e4 gfx::SurfaceFactoryOzone::GetInstance()
#3 0x000004bc85bf gfx::InitializeStaticGLBindings()
#4 0x000004bcc8fe gfx::GLSurface::InitializeOneOffImplementation()
#5 0x000004bcc88c gfx::GLSurface::InitializeOneOff()
#6 0x000003ed671f content::GpuMain()
#7 0x00000050a93b content::RunNamedProcessTypeMain()
#8 0x00000050b9f5 content::ContentMainRunnerImpl::Run()
#9 0x000000509e00 content::ContentMain()
#10 0x00000042612b main
#11 0x7f55249f176d __libc_start_main
#12 0x000000426029 <unknown>

[6369:6369:0708/155213:73787367853:ERROR:gpu_process_transport_factory.cc(387)] Failed to establish GPU channel.
[6369:6369:0708/155213:73787368067:ERROR:dri_surface_factory.cc(137)] Failed to create DRI connection
[6369:6369:0708/155213:73787368119:FATAL:software_output_device_ozone.cc(20)] Failed to initialize hardware in OZONE
#0 0x0000007c4903 base::debug::StackTrace::StackTrace()
#1 0x00000070807f logging::LogMessage::~LogMessage()
#2 0x000003cabd80 content::SoftwareOutputDeviceOzone::SoftwareOutputDeviceOzone()
#3 0x000003c97b9d content::CreateSoftwareOutputDevice()
#4 0x000003c98605 content::GpuProcessTransportFactory::CreateOutputSurface()
#5 0x00000133cf01 ui::Compositor::CreateOutputSurface()
#6 0x0000014ca23c cc::LayerTreeHost::CreateOutputSurface()
#7 0x00000153075d cc::SingleThreadProxy::CreateAndInitializeOutputSurface()
#8 0x0000014cba6d cc::LayerTreeHost::Composite()
#9 0x00000133ca29 ui::Compositor::Draw()
#10 0x000001342414 base::internal::RunnableAdapter<>::Run()
#11 0x000001341721 base::internal::InvokeHelper<>::MakeItSo()
#12 0x000001340749 base::internal::Invoker<>::Run()
#13 0x00000043a36d base::Callback<>::Run()
#14 0x000000711900 base::MessageLoop::RunTask()
#15 0x000000711a24 base::MessageLoop::DeferOrRunPendingTask()
#16 0x000000711f4b base::MessageLoop::DoWork()
#17 0x0000007b5215 base::MessagePumpLibevent::Run()
#18 0x00000071144f base::MessageLoop::RunHandler()
#19 0x000000749934 base::RunLoop::Run()
#20 0x0000038f45f9 content::BrowserMainLoop::MainMessageLoopRun()
#21 0x0000038f1eee content::BrowserMainLoop::RunMainMessageLoopParts()
#22 0x0000035870f0 content::BrowserMainRunnerImpl::Run()
#23 0x00000042a931 ShellBrowserMain()
#24 0x000000426ebd content::ShellMainDelegate::RunProcess()
#25 0x00000050a907 content::RunNamedProcessTypeMain()
#26 0x00000050b9f5 content::ContentMainRunnerImpl::Run()
#27 0x000000509e00 content::ContentMain()
#28 0x00000042612b main
#29 0x7f4f59a4b76d __libc_start_main
#30 0x000000426029 <unknown>

Aborted (core dumped)

[magreenblatt]

I think the error messages/stack traces that you posted contain a lot of good hints as to what the problem is. If you need more information/help then the chromium-dev mailing list is a better place to ask.