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
ze: tear down our context-bound state in zeContextDestroy prologue
The tracer was leaving its own L0 objects (event pools/events used as
the recycle pool, shadow command lists keyed by (ctx, device)) alive
inside the user's context. When the user app destroyed the context
before destroying a command list that had our injected events baked
into it (the Intel libomptarget L0 plugin does this at _dl_fini), the
following zeCommandListDestroy segfaulted inside libze_intel_gpu.so.
Add a zeContextDestroy prologue that, while the context is still
valid, walks _ze_cls / _ze_shadow_cls / _ze_event_pools and frees
everything we own keyed to the dying context.
0 commit comments