Bug#838913: libc6: There's probably a bug in libpthread, affecting several user programs.
control: tag -1 + moreinfo
control: retitle -1 libc6: memory allocation issues
On 2016-09-26 14:10, Fernando Santagata wrote:
> Package: libc6
> Version: 2.24-3
> Severity: important
>
> Dear Maintainer,
>
> One month ago everything worked fine on my Debian sid computer.
> After an update/dist-upgrade cycle in which libc6 was updated I started noticing some malfunctions.
> I couldn't use rakudobrew (the Perl6 installation program) anymore.
> I couldn't use the Selenium driver (a java program which drives the browser and provides an API to several programming languages).
> rsync started failing on big files.
> "java -version" fails.
>
> Yet, this doesn't appear to be a hardware problem: my computer works fine, even under heavy load. No other program seems to be affected, neither the browser (chrome), nor the music player (clementine), libreoffice, evince, gimp, etc.
>
> All the failing programs appear to be using threading. It shows even on small snippets of code: I'm collecting interesting snippets of Perl6 code; while most of them work fine, the ones that use threading are not working anymore.
>
> While I'm not able to debug libpthread, what I can show are just the symptoms.
>
> The command "java -version" outputs this:
>
> OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f570c3fb000, 172032, 0) failed; error='Cannot allocate memory' (errno=12)
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (mmap) failed to map 172032 bytes for committing reserved memory.
>
> I'm attaching the error logs as java-version.hs_err_pid12374.log and javaws.replay_pid12456.log.
>
> javaws outputs this:
> #
> # There is insufficient memory for the Java Runtime Environment to continue.
> # Native memory allocation (malloc) failed to allocate 32744 bytes for ChunkPool::allocate
> # An error report file with more information is saved as:
> # /home/nando/tmp/libc6_bug/hs_err_pid12456.log
> [thread 140120686573312 also had an error]
> [thread 140120688678656 also had an error]
> [thread 140121534289664 also had an error]
>
> [error occurred during error reporting , id 0xe0000001]
>
> I'm attaching the error log as javaws.hs_err_pid12456.log.
>
> Running rsync I got this error:
>
> ERROR: out of memory in flist_expand [sender]
> rsync error: error allocating core memory buffers (code 22) at util2.c(102) [sender=3.1.1]
>
Hmm, rsync doesn't use libpthread, so that clearly rules out a
libpthread issue. That said, all the example you gave fail to allocate
the memory correctly, either through malloc (glibc) or mmap (kernel)
which returns -ENOMEM. This points to either a kernel issue, or a
limitation of the memory using for example ulimit.
Can you please give us the output of "ulimit -a" on your system?
Thanks,
Aurelien
--
Aurelien Jarno GPG: 4096R/1DDD8C9B
aurelien@aurel32.net http://www.aurel32.net
Reply to: