Thanks. In my opinion this could warrant fixing in 20.04 LTS because:
- it's a regression from 18.04 LTS, so certain applications and usage patterns will break as users try to upgrade (which is what happened to me). - it affects several packages, specifically: libopenimageio, libopenvdb and python3-openvdb. libopenimageio is widely used, and python3-openvdb is currently not able to be imported because of this issue. Any other libraries that depend on openvdb will also be affected. - there's no need to upgrade to openvdb 7.x, and no code changes are required to the current 6.2.1 release either. It needs to be compiled with -DCONCURRENT_MALLOC=Tbballoc added to the CMake command line, and there's a patch available for this small change already. - this wouldn't be a high-risk update. I ended up working around my problem by setting the following environment variable that causes jemalloc to be loaded at process start, so it doesn't try to load itself later on in response to a dlopen() call. LD_PRELOAD=/usr/lib/x86_64-linux-gnu/libjemalloc.so.2 I've never worked directly with Ubuntu packages, but will take a look at the SRU Procedure and see if I can put something together. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1882998 Title: openvdb6.2 is non functionnal on Focal due to jemalloc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/jemalloc/+bug/1882998/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
