Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #996461
| From | Mathieu Malaterre <malat@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist |
| Subject | Bug#951704: ImportError: /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block |
| Date | 2020-02-20 12:00 +0100 |
| Message-ID | <zBRIJ-658-1@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Package: libjemalloc2 Version: 5.2.1-1 Severity: important Tags: patch I cannot import the pyopenvdb module on Debian sid (amd64). It fails like this: $ python3 Python 3.7.6 (default, Jan 19 2020, 22:34:52) [GCC 9.2.1 20200117] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import pyopenvdb Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block >>> Searching in the jemalloc bug report, I stumble upon: * https://github.com/jemalloc/jemalloc/issues/937 Would it be possible to build jemalloc with: --disable-initial-exec-tls [...] Disable the initial-exec TLS model for jemalloc's internal thread-local storage (on those platforms that support explicit settings). This can allow jemalloc to be dynamically loaded after program startup (e.g. using dlopen). Note that in this case, there will be two malloc implementations operating in the same process, which will almost certainly result in confusing runtime crashes if pointers leak from one implementation to the other. [...] ref: * https://github.com/jemalloc/jemalloc/blob/dev/INSTALL.md
Back to linux.debian.bugs.dist | Previous | Next | Find similar | Unroll thread
Bug#951704: ImportError: /lib/x86_64-linux-gnu/libjemalloc.so.2: cannot allocate memory in static TLS block Mathieu Malaterre <malat@debian.org> - 2020-02-20 12:00 +0100
csiph-web