-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
osrm-extract triggers the address sanitizer #2788
Comments
Just created an issue google/sanitizers#715 As a workaround the alignment could be completely removed or increased to 1024 in the failed test. |
Just updating from the linked issue, this is expected to go away with gcc >6.1.1. Thanks for looking into this @oxidase! |
@TheMarex committed to the branch fix for some "memory leaks" in TBB, that is correct behavior to prevent deinitialization fiasco for lazy-initialized Also there is another intended memory leak in osrm-datastore that requires change at https://github.com/Project-OSRM/osrm-backend/blob/master/include/storage/shared_memory.hpp#L70 |
Sadly GCC 6.1 and |
There is an access violation during the RTree generation. The error can be found here:
https://travis-ci.org/Project-OSRM/osrm-backend/jobs/153525915#L1824-L1882
I'm not sure if this is a false positive or points to bad code.
The text was updated successfully, but these errors were encountered: