Error in ozone-wayland chromium

[Amogh Kudari]

Hello Team,

     I am currently working for a project where I am building chromium version 51.0.2704. Chromium is using ozone-wayland for graphics port.

On executing the browser with --no-sandbox --url="http://www.google.com" I am facing following error.

Below is the log

========================================================================
[1111/111425:ERROR:browser_main_loop.cc(219)] Running without the SUID sandbox! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux_suid_sandbox_development.md for more information on developing with the sandbox on.
[1111/111425:ERROR:sandbox_linux.cc(334)] InitializeSandbox() called with multiple threads in process gpu-process
[1111/111425:WARNING:ipc_message_attachment_set.cc(57)] MessageAttachmentSet destroyed with unconsumed descriptors: 0/1
surface                : 90 created
[1111/111425:ERROR:desktop_window_tree_host_ozone.cc(568)] Not implemented reached in virtual void views::DesktopWindowTreeHostOzone::SetWindowIcons(const gfx::ImageSkia&, const gfx::ImageSkia&)
[1111/111426:ERROR:gles2_cmd_decoder.cc(14364)] [.CommandBufferContext.DisplayCompositor-0x13d700065b00]GL ERROR :GL_INVALID_ENUM : glTexStorage2DEXT:
[1111/111426:ERROR:gles2_cmd_decoder.cc(14364)] [.CommandBufferContext.DisplayCompositor-0x13d700065b00]GL ERROR :GL_INVALID_ENUM : glTexStorage2DEXT:

[1111/111426:ERROR:gles2_cmd_decoder.cc(14028)] [.CommandBufferContext.CompositorWorker-0x13d700065c60]GL ERROR :GL_INVALID_OPERATION : glCopySubTextureCHROMIUM: destination texture is not defined
[1111/111426:ERROR:gles2_cmd_decoder.cc(14028)] [.CommandBufferContext.CompositorWorker-0x13d700065c60]GL ERROR :GL_INVALID_OPERATION : glCopySubTextureCHROMIUM: destination texture is not defined
[1111/111426:ERROR:gles2_cmd_decoder.cc(14028)]

[1111/111426:ERROR:gles2_cmd_decoder.cc(7857)] [.CommandBufferContext.DisplayCompositor-0x13d700065b00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.
[1111/111426:ERROR:gles2_cmd_decoder.cc(7857)] [.CommandBufferContext.DisplayCompositor-0x13d700065b00]RENDER WARNING: texture bound to texture unit 0 is not renderable. It maybe non-power-of-2 and have incompatible texture filtering.

SetDestinationRectangle: surface ID (90), Width (800), Height (600)
SetSourceRectangle     : surface ID (90), Width (800), Height (600)
SetVisibility          : surface ID (90), ILM_TRUE
layerAddSurface        : surface ID (90) is added to layer ID (100)
[1111/111426:ERROR:gles2_cmd_decoder.cc(14364)] [.CommandBufferContext.RenderCompositor-0x12236617b000]GL ERROR :GL_INVALID_ENUM : glTexStorage2DEXT:
[1111/111426:ERROR:gles2_cmd_decoder.cc(14364)] [.CommandBufferContext.RenderCompositor-0x12236617b000]GL ERROR :GL_INVALID_ENUM : glTexStorage2DEXT:

========================================================================



I have already googled for solution, most of them say to disable gpu using --disable-gpu or --disable-gpu-compositing.

But the browser process crashes, with the following message, saying you cannot disable gpu when using wayland.


================================================

[1111/112207:FATAL:display.cc(236)] The browser process has attempted to start the GPU process in software rendering mode. Software rendering is not supported in Ozone-Wayland, so this is fatal. Usually this error occurs because the GPU process crashed in hardware rendering mode, often due to failure to initialize EGL. To debug the GPU process, start Chrome with --gpu-startup-dialog so that the GPU process pauses on startup, then attach to it with 'gdb -p' and run the command 'signal SIGUSR1' in order to unpause it. If you have xterm then it is easier to run 'chrome --no-sandbox --gpu-launcher='xterm -title renderer -e gdb --eval-command=run --args''

================================================


Please let me know, what is the reason for it and how can it be solved.

Thanks in advance.

Regards,
Amogh.

[Robert Kroeger]

[BCC chromium-dev, redirecting to ozone-dev]

comments inline

afaik, you need a working GL stack for ozone-wayland. Build osmesa and try running chrome with --use-gl=osmesa

Rob.

 

Thanks in advance.

Regards,
Amogh.

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAEyxnoT7K5cVVuxqXxQj8ORMLK1jcD8X1w6JLnYGHiAp7UsKcg%40mail.gmail.com.