The issue needs to be tested by using a gamepad and ET-team doesn't have a gamepad to test the issue. Hence, forwarding the issue to inhouse team for further triaging.

Thanks...!!

Tested on latest Stable #70.0.3538.77 and Canary #72.0.3602.0 on Debian Rodete, Windows 10 and Mac 10.13.6 and was able to reproduce the issue mentioned. 

Using the per-revision bisect providing the bisect results,
Good build: 69.0.3496.0
Bad build: 69.0.3497.0

You are probably looking for a change made after 576621 (known good), but no later than 576622 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspect as some perf builds might get missing due to failure.
https://chromium.googlesource.com/chromium/src/+log/22179d3943015494b82b0e462f34e5007a0b7857..1ce671509c922ab463f3c2c9aff736745ade2850

From the CL above, assigning the issue to the owner concerned 

@alexilin: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-URL: https://chromium-review.googlesource.com/1142161

Sample Crash ID: 2458340f4b5b2074

Thanks!

Deleted: 901646.PNG 14.9 KB

	901646.PNG 14.9 KB View Download

Issue is also observed on Sony Wireless Controller as well (Tested on Model CUH-ZCT1E)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/b76c606d8656f4373ac8591d6300a93ffc384154

commit b76c606d8656f4373ac8591d6300a93ffc384154
Author: Alexandr Ilin <alexilin@chromium.org>
Date: Wed Nov 28 10:27:12 2018

Remove the PlatformSharedMemoryRegion permissions check on NaCl

To perform the permissions check on NaCl, we mmap() a shared memory region as
writable and check the return value to know if map failed. It's expected that
the call would fail if the region has read-only permissions.

Unfortunately, NaCl doesn't handle failure cases gracefully and crashes
instead of returning error value [1], [2].

This means, that an attempt to check permissions on a read-only shared memory
region always leads to a crash. This CL removes the check altogether to allow
the NaCl processes to use read-only shared memory.

[1] Posix: https://cs.chromium.org/chromium/src/native_client/src/trusted/service_runtime/sys_memory.c?rcl=f701a90597fc85979319447c0cd44c3b52201c78&l=868
[2] Win: https://cs.chromium.org/chromium/src/native_client/src/shared/imc/win/nacl_shm.cc?rcl=f701a90597fc85979319447c0cd44c3b52201c78&l=112

Bug:  901646 
Change-Id: I1f0cee4f7edae0390701320f5061470d62240186
Reviewed-on: https://chromium-review.googlesource.com/c/1352312
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Commit-Queue: Alexandr Ilin <alexilin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#611630}
[modify] https://crrev.com/b76c606d8656f4373ac8591d6300a93ffc384154/base/memory/platform_shared_memory_region_posix.cc

The issue should be fixed in Chrome M72 and it should be included in the next Canary release.

It seems to be late for merging the fix into M71, since we've already passed the stable cut.

Tested on latest Canary #72.0.3625.0 and issue doesn't seems to be reproduced on Windows 10, Mac and Debian Rodete. Hence marking the issue with TE-Verified labels.

Thanks!