From glancing through that code, that flag seems to only enable a
single LOG(FATAL) at sandbox initialization time. Unfortunately, due
to implementation details of the Linux sandbox, there are certain
types of failures which we cannot easily log (the biggest example
being attempts to open files which do not exist inside of the chroot).
I would probably try to strace the GPU process and see if there are
any failed attempts to open files that look like they might be
performance-sensitive - for example, opening /proc/cpuinfo to
determine whether some optimizations might be enabled. Failing that,
we can also try to selectively disable parts of the sandbox
(unfortunately not easily flag controlled) to try and narrow down
which restrictions are causing the performance issue. Happy to help
look deeper if there isn't an easy cause!
Thanks,
Ricky
On Mon, Aug 17, 2015 at 12:24 PM, Sunny Sachanandani