New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

libyuv /proc/cpuinfo detect within Chrome sandbox #345

Open

GoogleCodeExporter opened this issue Sep 11, 2015 · 3 comments

Labels

auto-migrated Priority-Medium Type-Defect

GoogleCodeExporter commented Sep 11, 2015

Neon instruction set is optional and detection is via the file /proc/cpuinfo
This file can not be read within Chrome's sandbox.

r1037 attempts to read the file, but if it can not be read and the NEON code 
has been built in, Neon is assumed to be true.

Find a better way to detect Neon that is sandbox friendly.

Original issue reported on code.google.com by [email protected] on 22 Jul 2014 at 5:35

The text was updated successfully, but these errors were encountered:

GoogleCodeExporter added Priority-Medium Type-Defect auto-migrated labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment