Comment 4 for bug 1882998
Revision history for this message
| Richard Viney (richard-nz) wrote Re: openvdb6.2 is non functionnal on Focal due to jemalloc | #4 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
AFAICT this issue was introduced in OpenVDB 6.2.0 when it started linking in jemalloc all the time, including when being built as a shared library.
My understanding is that shared libraries should absolutely not be doing this, as safely linking allocators such as jemalloc into a shared library is very tricky to do correctly, and can also make it impossible to use the shared library dynamically via `dlopen`.
In my case I ran into this via OpenImageIO which had a dependency on libopenvdb.so.6.2, and I was getting the error "/usr/lib/
OpenVDB addresses this as of v7.1.0, though this hasn't actually been released. The changelog [1] reads:
- jemalloc/tbbmalloc are no longer linked into library artifacts of the
OpenVDB CMake build. The CONCURRENT_MALLOC CMake option now only applies
to the executables.
My understanding is that this is fixed in the proposed libopenvdb package for groovy which uses OpenVDB v7, but getting that working as a dependency of OpenImageIO on a focal system might be tricky. For my situation I'm intending to build OpenImageIO from source, link it statically, and exclude OpenVDB at build time because I don't actually need it anyway.
Hopefully there's a backport of the fix removing jemalloc to the OpenVDB 6.x series that can become part of an update to focal, or perhaps focal could use the proposed package for groovy.
[1] https:/