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
Currently the address sanitizer CI job added in #972 explicitly disables detect_stack_use_after_return (default is also off, but this is to protect from a change to the default). It seems like enabling this option leads to some tests simply failing (not with warnings from address sanitizer, but with segfaults etc.). E.g.:
Investigate what is causing the problem and/or see if a newer version of sanitizers don't trigger this issue. It seems like this may be related to excessive memory usage by address sanitizer.
The text was updated successfully, but these errors were encountered:
Currently the address sanitizer CI job added in #972 explicitly disables
detect_stack_use_after_return
(default is also off, but this is to protect from a change to the default). It seems like enabling this option leads to some tests simply failing (not with warnings from address sanitizer, but with segfaults etc.). E.g.:Investigate what is causing the problem and/or see if a newer version of sanitizers don't trigger this issue. It seems like this may be related to excessive memory usage by address sanitizer.
The text was updated successfully, but these errors were encountered: