Issue metadata
Sign in to add a comment
|
Egl bad attrib+dijoint timer exposure+Linux/Ubuntu doesnt like hardware accel of gpu mem
Reported by
jonpalme...@gmail.com,
Apr 20 2018
|
||||||||||||||||||
Issue descriptionWhat were you doing? Cross referencing about:gpu with flags to optimize performance and continue the constant improvement to my browsing experience. What happened? Each time i change the native memory buffer flag my browser would flicker and i've found no config to make the flag support my framework/runtime. Bottom of gpu report reads egl failed bad attrib. Studying this i think maybe you guys should put some of the clout you've bolstered in the intelligence community into brokering a good deal of some kind with Adobe. Or, I would like to requst access to the bugs in the subject of this correspondnce because my own clearance now seems to be limited by bug number. Please, ref. my gpu report for my need to know and withdraw the restriction of my access to the aforementioned bugs, because i would like to study the commit hist. for personal edification and to compare it with the timeframe and totals of reports that appear in my search results. What did you expect instead? I believed that i could use the chrome program in unison with my local HW to maximize their poss. shared abilities. Also, thank you for your petitioning the powers recently, i saw that as good faith. Cheers! If you have precise reproduction steps, please include them above. If you have a screenshot demonstrating your feedback, please make sure it does not include any confidential information and then attach it.
,
Apr 26 2018
,
Jul 27
Could you describe the steps to reproduce the failure, as well as what is the expected behavior? Could you also include your Chrome version and about:gpu page? Thank you. |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by seanmccullough@chromium.org
, Apr 25 2018