You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You should get a SIGSEGV sometime during TouchspotController's destruction
This issue is that TouchspotController doesn't hold on to a reference to the allocator it created its graphics buffer with. So after it creates a buffer and some time before the buffer is destroyed, the module is unloaded. Once we try to destroy TouchspotController and try to destroy the buffer, it tries to call unloaded code, blowing up the whole thing.
The quickest workaround is to keep a reference to the allocator, which itself keeps the module alive. The better solution would be to tie the lifetime of the module to the lifetime of whatever is using it.
The text was updated successfully, but these errors were encountered:
How to reproduce:
MIRENG-883/support-mouse-keys
TouchspotController
's destructionThis issue is that
TouchspotController
doesn't hold on to a reference to the allocator it created its graphics buffer with. So after it creates a buffer and some time before the buffer is destroyed, the module is unloaded. Once we try to destroyTouchspotController
and try to destroy the buffer, it tries to call unloaded code, blowing up the whole thing.The quickest workaround is to keep a reference to the allocator, which itself keeps the module alive. The better solution would be to tie the lifetime of the module to the lifetime of whatever is using it.
The text was updated successfully, but these errors were encountered: