[ozone-dev] Re: [chromium-dev] headless ozone doesn't create files

[Robert Kroeger]

[bcc chromium-dev, cc ozone-dev instead]

I'm running content_shell on trusty and it doesn't create files in the
./content_shell --ozone-platform=headless --ozone-dump-file=/tmp
--no-sandbox <URL>

Perhaps the code has regressed. I have filed http://crbug.com/781268 to
track. What are the gn args for your build? Does this occur regardless of
the target URL? And what console output do you get? I will try this out and
update the bug.

Rob.

It works fine when started with --ozone-platform=x11
I tried ozone_demo with the headless platform driver and it works as
expected
I also noticed that when running content_shell HeadlessSurfaceFactory::CreateCanvasForWidget
is never called
Is it a known issue? What was the last tag when it was working?
Thanks
--
--
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
To view this discussion on the web visit https://groups.google.com/a/
chromium.org/d/msgid/chromium-dev/f54693fa-9421-48cb-a020-
5ebf654fc7c7%40chromium.org
<https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/f54693fa-9421-48cb-a020-5ebf654fc7c7%40chromium.org?utm_medium=email&utm_source=footer>
.

[m***@gmail.com]

./content_shell --ozone-platform=headless  --ozone-dump-file=/tmp --no-sandbox <URL>
Perhaps the code has regressed. I have filed http://crbug.com/781268 to track. What are the gn args for your build? Does this occur regardless of the target URL? And what console output do you get? I will try this out and update the bug.

It does look like a regression - I tried 60.0.3112.78 and it works with the same gn args.

There is no console output (unless I turn on logging) and it happens with every URL I tried.

My args:

use_ozone=true
toolkit_views=false
ozone_auto_platforms=false
ozone_platform_headless=true
ozone_platform_x11=true
use_debug_fission=false
treat_warnings_as_errors=false
enable_vr=false
media_use_ffmpeg=false
use_libpci=false
use_cups=false
use_udev=false
use_dbus=false
use_glib=false
use_gio=false
use_pulseaudio=false
use_alsa=false
use_kerberos=false
remove_webcore_debug_symbols = true
enable_nacl = false
cc_wrapper="ccache"
clang_use_chrome_plugins=false

['Robert Kroeger' via Ozone-Dev]

I'm running content_shell on trusty and it doesn't create files in
./content_shell --ozone-platform=headless --ozone-dump-file=/tmp

--no-sandbox <URL>

Perhaps the code has regressed. I have filed http://crbug.com/781268 to

track. What are the gn args for your build? Does this occur regardless of
the target URL? And what console output do you get? I will try this out and
update the bug.
It does look like a regression - I tried 60.0.3112.78 and it works with the same gn args.

:-(

I'll look into this if no one beats me to it.

There is no console output (unless I turn on logging) and it happens with
every URL I tried.
use_ozone=true
toolkit_views=false
ozone_auto_platforms=false
ozone_platform_headless=true
ozone_platform_x11=true
use_debug_fission=false
treat_warnings_as_errors=false
enable_vr=false
media_use_ffmpeg=false
use_libpci=false
use_cups=false
use_udev=false
use_dbus=false
use_glib=false
use_gio=false
use_pulseaudio=false
use_alsa=false
use_kerberos=false
remove_webcore_debug_symbols = true
enable_nacl = false
cc_wrapper="ccache"
clang_use_chrome_plugins=false

['Kyle Charbonneau' via Ozone-Dev]

Add --disable-gpu and it should work. content_shell is using GL rendering
instead of software rendering, so that file doesn't get written to.

Kyle

On Mon, Nov 6, 2017 at 4:57 PM, 'Robert Kroeger' via Ozone-Dev <

Post by 'Robert Kroeger' via Ozone-Dev

I'm running content_shell on trusty and it doesn't create files in
./content_shell --ozone-platform=headless --ozone-dump-file=/tmp

--no-sandbox <URL>

Perhaps the code has regressed. I have filed http://crbug.com/781268

to track. What are the gn args for your build? Does this occur regardless
of the target URL? And what console output do you get? I will try this out
and update the bug.
It does look like a regression - I tried 60.0.3112.78 and it works with the same gn args.

:-(
I'll look into this if no one beats me to it.

There is no console output (unless I turn on logging) and it happens with
every URL I tried.
use_ozone=true
toolkit_views=false
ozone_auto_platforms=false
ozone_platform_headless=true
ozone_platform_x11=true
use_debug_fission=false
treat_warnings_as_errors=false
enable_vr=false
media_use_ffmpeg=false
use_libpci=false
use_cups=false
use_udev=false
use_dbus=false
use_glib=false
use_gio=false
use_pulseaudio=false
use_alsa=false
use_kerberos=false
remove_webcore_debug_symbols = true
enable_nacl = false
cc_wrapper="ccache"
clang_use_chrome_plugins=false
--

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

[Michael Spang]

It should probably still write the file in the GL case, by subclassing the
mesa surface. Since that's where the output is intended to actually go.

The file writing is pretty hacky though.. it continuously truncates the
same file and there's no mechanism to tell when it is done other than
passing it through the png decoder and seeing if that works. Please don't
rely on this feature :)

Michael

On Mon, Nov 6, 2017 at 5:25 PM 'Kyle Charbonneau' via Ozone-Dev <

Post by 'Kyle Charbonneau' via Ozone-Dev
Add --disable-gpu and it should work. content_shell is using GL rendering
instead of software rendering, so that file doesn't get written to.
Kyle
On Mon, Nov 6, 2017 at 4:57 PM, 'Robert Kroeger' via Ozone-Dev <

Post by 'Robert Kroeger' via Ozone-Dev

I'm running content_shell on trusty and it doesn't create files in
./content_shell --ozone-platform=headless --ozone-dump-file=/tmp

--no-sandbox <URL>

Perhaps the code has regressed. I have filed http://crbug.com/781268

to track. What are the gn args for your build? Does this occur regardless
of the target URL? And what console output do you get? I will try this out
and update the bug.
It does look like a regression - I tried 60.0.3112.78 and it works with
the same gn args.

:-(
I'll look into this if no one beats me to it.

There is no console output (unless I turn on logging) and it happens
with every URL I tried.
use_ozone=true
toolkit_views=false
ozone_auto_platforms=false
ozone_platform_headless=true
ozone_platform_x11=true
use_debug_fission=false
treat_warnings_as_errors=false
enable_vr=false
media_use_ffmpeg=false
use_libpci=false
use_cups=false
use_udev=false
use_dbus=false
use_glib=false
use_gio=false
use_pulseaudio=false
use_alsa=false
use_kerberos=false
remove_webcore_debug_symbols = true
enable_nacl = false
cc_wrapper="ccache"
clang_use_chrome_plugins=false
--

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

[Michael Spang]

If we really cared about this feature it would record video instead.
Starter project for someone :)

Post by Michael Spang
It should probably still write the file in the GL case, by subclassing the
mesa surface. Since that's where the output is intended to actually go.
The file writing is pretty hacky though.. it continuously truncates the
same file and there's no mechanism to tell when it is done other than
passing it through the png decoder and seeing if that works. Please don't
rely on this feature :)
Michael
On Mon, Nov 6, 2017 at 5:25 PM 'Kyle Charbonneau' via Ozone-Dev <

Post by 'Kyle Charbonneau' via Ozone-Dev
Add --disable-gpu and it should work. content_shell is using GL rendering
instead of software rendering, so that file doesn't get written to.
Kyle
On Mon, Nov 6, 2017 at 4:57 PM, 'Robert Kroeger' via Ozone-Dev <

Post by 'Robert Kroeger' via Ozone-Dev

I'm running content_shell on trusty and it doesn't create files in
./content_shell --ozone-platform=headless --ozone-dump-file=/tmp

--no-sandbox <URL>

Perhaps the code has regressed. I have filed http://crbug.com/781268

to track. What are the gn args for your build? Does this occur regardless
of the target URL? And what console output do you get? I will try this out
and update the bug.
It does look like a regression - I tried 60.0.3112.78 and it works with
the same gn args.

:-(
I'll look into this if no one beats me to it.

There is no console output (unless I turn on logging) and it happens
with every URL I tried.
use_ozone=true
toolkit_views=false
ozone_auto_platforms=false
ozone_platform_headless=true
ozone_platform_x11=true
use_debug_fission=false
treat_warnings_as_errors=false
enable_vr=false
media_use_ffmpeg=false
use_libpci=false
use_cups=false
use_udev=false
use_dbus=false
use_glib=false
use_gio=false
use_pulseaudio=false
use_alsa=false
use_kerberos=false
remove_webcore_debug_symbols = true
enable_nacl = false
cc_wrapper="ccache"
clang_use_chrome_plugins=false
--

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