Issue 552068 in chromium: --enable-native-gpu-memory-buffers flag not recognized on Linux

3,211 views
Skip to first unread message

chro...@googlecode.com

unread,
Nov 5, 2015, 5:44:30 PM11/5/15
to chromi...@chromium.org
Status: Unconfirmed
Owner: ----
Labels: Pri-2 Via-Wizard Type-Feature OS-Linux

New issue 552068 by axfe...@gmail.com: --enable-native-gpu-memory-buffers
flag not recognized on Linux
https://code.google.com/p/chromium/issues/detail?id=552068

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like
Gecko) Chrome/48.0.2552.0 Safari/537.36

Steps to reproduce the problem:
1. Launch chrome with --enable-native-gpu-memory-buffers (and
--enable-zero-copy)
2. Check chrome://gpu
3. GpuMemoryBufferStatus reports software-only

What is the expected behavior?
GpuMemoryBufferStatus reports hardware acceleration

What went wrong?
I suspect that this is disabled at compile time on non-ChromeOS Linux the
way that vaapi is, such that it can't be reenabled through flags. If so,
can you please not do this? If not, I'm not sure what the issue is.

Did this work before? N/A

Chrome version: 48.0.2552.0 Channel: dev
OS Version: 3.18 / Gnome 3.18
Flash Version: Shockwave Flash 19.0 r0

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

chro...@googlecode.com

unread,
Nov 6, 2015, 2:16:57 AM11/6/15
to chromi...@chromium.org
Updates:
Status: Untriaged

Comment #1 on issue 552068 by msrchan...@chromium.org:
--enable-native-gpu-memory-buffers flag not recognized on Linux
https://code.google.com/p/chromium/issues/detail?id=552068

(No comment was entered for this change.)

chro...@googlecode.com

unread,
Jan 15, 2016, 12:11:18 AM1/15/16
to chromi...@chromium.org
Updates:
Labels: Cr-Internals-GPU

Comment #2 on issue 552068 by cbiesin...@chromium.org:

chro...@googlecode.com

unread,
Jan 15, 2016, 12:14:18 AM1/15/16
to chromi...@chromium.org

Comment #3 on issue 552068 by axfe...@gmail.com:
--enable-native-gpu-memory-buffers flag not recognized on Linux
https://code.google.com/p/chromium/issues/detail?id=552068

On inspection it appears to be blacklisted for mesa only, but indeed at
compile time. Haven't tested on Linux NVIDIA.

chro...@googlecode.com

unread,
Jan 15, 2016, 1:43:04 PM1/15/16
to chromi...@chromium.org

Comment #4 on issue 552068 by axfe...@gmail.com:
--enable-native-gpu-memory-buffers flag not recognized on Linux
https://code.google.com/p/chromium/issues/detail?id=552068

Appears not to work on Nvidia either:

GpuMemoryBuffer Status
ATC Software only
ATCIA Software only
DXT1 Software only
DXT5 Software only
ETC1 Software only
R_8 Software only
RGBA_4444 Software only
RGBX_8888 Software only
RGBA_8888 Software only
BGRX_8888 Software only
BGRA_8888 Software only
YUV_420 Software only
YUV_420_BIPLANAR Software only
UYVY_422 Software only

Version Information
Data exported 1/15/2016, 10:10:28 AM
Chrome version Chrome/48.0.2564.79
Operating system Linux 3.19.0-39-generic
Software rendering list version 10.16
Driver bug list version 8.32
ANGLE commit id unknown hash
2D graphics backend Skia
Command Line Args
--ppapi-flash-path=/usr/lib/pepflashplugin-installer/libpepflashplayer.so
--ppapi-flash-version=20.0.0.267 --enable-pinch
--enable-native-gpu-memory-buffers --flag-switches-begin
--enable-download-resumption --enable-gpu-rasterization
--enable-smooth-scrolling --enable-zero-copy
--gpu-rasterization-msaa-sample-count=0 --flag-switches-end

Driver Information
Initialization time 500
In-process GPU false
Sandboxed true
GPU0 VENDOR = 0x10de, DEVICE= 0x17c2
Optimus false
AMD switchable false
Driver vendor NVIDIA
Driver version 358.16
Driver date
Pixel shader version 4.50
Vertex shader version 4.50
Max. MSAA samples 32
Machine model name
Machine model version
GL_VENDOR NVIDIA Corporation
GL_RENDERER GeForce GTX TITAN X/PCIe/SSE2
GL_VERSION 4.5.0 NVIDIA 358.16

Your documentation of the feature suggests this might only be implemented
on Intel, and given that it's explicitly blacklisted on Mesa, and Mesa is
the only real Intel GPU implementation on Linux, maybe it just doesn't work
at all on Linux currently?

chro...@googlecode.com

unread,
Jan 19, 2016, 4:31:52 PM1/19/16
to chromi...@chromium.org
Updates:
Status: WontFix

Comment #6 on issue 552068 by rev...@chromium.org:
--enable-native-gpu-memory-buffers flag not recognized on Linux
https://code.google.com/p/chromium/issues/detail?id=552068

Working as expected as native GMBs are not yet supported on Linux.
Reply all
Reply to author
Forward
0 new messages