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
This results in a AddressSanitizer: heap-use-after-free error. This seems to be the result of removing the name from the registry table
tab.remove(are.name);
This is the error that led to the nightly failures that caused us to skip testNA in #2726. But this doesn't just apply to categorical, it happens when unregistering any object
The text was updated successfully, but these errors were encountered:
This PR (fixesBears-R-Us#2737) changes `registry.lookup` to return a shared object instead of borrowed. This make it so later references to `gre` in `unregisterMsg` don't cause us to access freed memory
When building chapel with the address sanitizer (instructions here). We see an access after free error when something gets unregistered
This results in a
AddressSanitizer: heap-use-after-free
error. This seems to be the result of removing the name from the registry tableThis is the error that led to the nightly failures that caused us to skip
testNA
in #2726. But this doesn't just apply to categorical, it happens when unregistering any objectThe text was updated successfully, but these errors were encountered: