Please note this also affects gridengine-drmaa1.0, where libdrmaa.so is linked
vs libjemalloc.so.2,
and attempts to dlopen() libdrmaa fail with 'cannot allocate memory in static
TLS block'.
According to https://github.com/jemalloc/jemalloc/issues/1237, this can be
fixed by configuring
jemalloc
** Changed in: jemalloc (Ubuntu)
Importance: Undecided => Medium
** Changed in: jemalloc (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: openvdb (Ubuntu)
Importance: Undecided => Medium
** Changed in: openvdb (Ubuntu Focal)
Importance: Undecided => Medium
--
You recei
** Also affects: jemalloc (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: openvdb (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
Please find attached a debdiff for focal
** Patch added: "Remove jemalloc dependency from openvdb"
https://bugs.launchpad.net/ubuntu/+source/openvdb/+bug/1882998/+attachment/5409211/+files/openvdb_6.2.1-8ubuntu2.debdiff
--
You received this bug notification because you are a member of Ubuntu
[Impact]
* This issue causes apps to be unable to dlopen libopenvdb6.2 or any
shared libraries that depend directly or indirectly on libopenvdb6.2.
Notably this includes libopenimageio2.1 and anything that depends on it.
The python3-openvdb package also doesn't work in focal at present
because of
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
p
openvdb (7.0.0-1) experimental; urgency=medium
...
* d/control: Remove dependency to jemalloc. See #951704 for details
...
https://salsa.debian.org/multimedia-
team/openvdb/-/commit/ac393d95aa19d29c23a97dca1ace23061ebe5c17
--
You received this bug notification because you are a member of Ubunt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. However, I am closing it because the bug has been fixed
in the latest development version of Ubuntu.
If you need a fix for the bug in previous versions of Ubuntu, please
perform as much as possible of the SRU Proce
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
** Changed in: jemalloc (Debian)
Status: Unknown => New
--
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 notific
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: jemalloc (Ubuntu)
Status: New => Confirmed
--
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:
** Bug watch added: Debian Bug tracker #951704
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951704
** Also affects: jemalloc (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951704
Importance: Unknown
Status: Unknown
** Also affects: jemalloc (Ubuntu)
Importa
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: openvdb (Ubuntu)
Status: New => Confirmed
--
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:
o
13 matches
Mail list logo
