Might be worth investigating. There is a known synchronization issue on Mac OS X where the gamepad monitor thread will continue to deliver events after shutdown was requested because the requesting thread doesn't actually `wait()` on the shutdown to complete before it deletes all its state objects. Normally, this is not a huge problem since the `GamepadManager` will just silently ignore these extraneous events; however, in some cases it can do weird things... This may be one of them. It has been on my todo list forever to fix this, but there's just never any time to work on gamepad stuff these days.
Bug 1870379 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Might be worth investigating. There is a known synchronization issue on Mac OS X where the gamepad monitor thread will continue to deliver events after shutdown was requested because the requesting thread doesn't actually `wait()` on the shutdown to complete before it deletes all its state objects. Normally, this is not a huge problem since the `GamepadManager` will just silently ignore events if it's already deleted everything; however, in some cases it can do weird things... This may be one of them. It has been on my todo list forever to fix this, but there's just never any time to work on gamepad stuff these days.