Re: [chromium-dev] Error in ozone-wayland chromium

[Robert Kroeger]

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

comments inline

On Friday, October 27, 2017, Amogh Kudari <amogh....@gmail.com> wrote:

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.

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.

[Amogh Kudari]

Hi Robert,

         Thanks for your response. 

         I am using opengl (libGLESv2.so.2) with ozone wayland. 

        Correct me, if I am wrong, I think this library libGLESv2.so.2 provides the GL stack required for drawing and graphics, similar to mesa, which is 3D graphics library.

Currently for compilation I am using the following GYP_DEFINES

use_ozone=1 ozone_platform_wayland=1

ozone_platform_wayland=1

use_wayland_egl=1 

but still getting the same error.

Since I am already using GLE's, Is it still necessary to build osmesa and then run chrome with chrome with --use-gl=osmesa

Regards,

Amogh.

[Antonio Gomes]

Hi Amogh. Some comments inline.

On 31/10/2017 08:03, Amogh Kudari wrote:
> Hi Robert,
>
>          Thanks for your response.
>          I am using opengl (libGLESv2.so.2) with ozone wayland.
>         Correct me, if I am wrong, I think this library libGLESv2.so.2
> provides the GL stack required for drawing and graphics, similar to
> mesa, which is 3D graphics library.
>
> Currently for compilation I am using the following GYP_DEFINES

For the sake of record, I believe you meant GN parameters (not GYP), but
at m51 timeframe GYP was still a thing, so it might be GYP indeed.

:-)

> use_ozone=1 ozone_platform_wayland=1
> ozone_platform_wayland=1
> use_wayland_egl=1
>
> but still getting the same error.
>
> Since I am already using GLE's, Is it still necessary to build osmesa
> and then run chrome with chrome with --use-gl=osmesa
>
>
> Regards,
> Amogh.
>
> On Mon, Oct 30, 2017 at 9:20 PM, Robert Kroeger <rjkr...@chromium.org
> <mailto:rjkr...@chromium.org>> wrote:
>
> [BCC chromium-dev, redirecting to ozone-dev]
>
> comments inline
>
>
> On Friday, October 27, 2017, Amogh Kudari <amogh....@gmail.com

> <mailto:amogh....@gmail.com>> wrote:
>
> 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.

In m51 timeframe (I believe trunk is m64 today), there were a limited
ozone/wayland support in Chromium's trunk, and it was totally ChromeOS
oriented. Even in Ozone/Wayland ChromeOS offdevice builds (to be ran on
desktop for testing), there were runtime errors, fixed by

https://codereview.chromium.org/2389053003/
https://codereview.chromium.org/2387063002/ ([ozone/wayland] Use
SurfacelessEGL when supported)

This is hard to diagnose given the such old codebase.

Questions:

1- Does this contain code from https://github.com/intel/ozone-wayland ?
Note that the last release was based on m48, there were an effort to
upversion it to m53 (the the branches on GitHub), and there is another
ongoing effort to upversion it to m60 (cc jose dapena).

2- Are you aware of github.com/igalia/chromium ?

-
Antonio

[Bo Gao]

I think this is what you want to set for ozone-wayland:

  use_ozone=1

  ozone_auto_platforms=0

  ozone_platform_wayland=1

  ozone_platform="wayland"

  use_wayland_egl=1

Also what version of Wayland and Wayland compositor (Weston?) you're running? Better to check the version of //third_party/wayland-protocol in m51.

Try running with --single-process to see if it helps. At least it would be easier to debug the renderer in the same process.

Regards,

Bo

--
You received this message because you are subscribed to the Google Groups "Ozone-Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ozone-dev+...@chromium.org.

[Amogh Kudari]

Hi Bo, Robert and Antonio,

      Thanks for your inputs. You were right about Wayland and weston. I did check if there was any issue with respect to weston and wayland graphics, which came out to be true.
I had to make changes in service file to start weston(usr/bin/weston) with connector id using --connector argument.

Thanks and Regards,
Amogh.

To unsubscribe from this group and stop receiving emails from it, send an email to ozone-dev+unsubscribe@chromium.org.