| commit | 96e83f95eef5be8e1f64a1a2e61810cb7b82ff5c | |
| author | Chris Robinson <chris.kcat@gmail.com> | |
| Fri, 29 Jul 2016 15:02:02 +0000 (29 08:02 -0700) | ||
| committer | Chris Robinson <chris.kcat@gmail.com> | |
| Fri, 29 Jul 2016 15:02:02 +0000 (29 08:02 -0700) | ||
| tree | c36d687b406fef5b64f9f881c59d15aeec73aae7 | treesnapshot (tar.gz zip) |
| parent | 5e11a738c6b18a367070450ec46dfb714fe433d7 | commitdiff |
Don't try freeing the context in ReleaseThreadCtx
Unfortunately on certain systems, the TLS callback is called in a restricted
context, and isn't allowed to access certain messaging sub-systems. Such sub-
systems may be used if the thread's context is freed, in turn freeing the
device, which it tries to close.
Ideally, the app shouldn't have tried to destroy a context while it was still
current on a thread, or even leave a context current on a thread that's being
destroyed,. So for now, release the context ref and print an ERR that it might
be leaked.
Unfortunately on certain systems, the TLS callback is called in a restricted
context, and isn't allowed to access certain messaging sub-systems. Such sub-
systems may be used if the thread's context is freed, in turn freeing the
device, which it tries to close.
Ideally, the app shouldn't have tried to destroy a context while it was still
current on a thread, or even leave a context current on a thread that's being
destroyed,. So for now, release the context ref and print an ERR that it might
be leaked.
| Alc/ALc.c | diffblobblamehistory |