This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug malloc/21273] insufficient memory with more then 10 GB free memory


https://sourceware.org/bugzilla/show_bug.cgi?id=21273

--- Comment #5 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Carlos O'Donell from comment #4)
> (In reply to Adhemerval Zanella from comment #3)
> > As for comment #2 neither comment added any useful information to indicate
> > it might either be a glibc issue or any way to try reproduce or pinpoint any
> > possible issue.  If you indeed have any information indicating a glibc issue
> > (backtrace, testcase, etc.), please open a new bug or reopen issue.
> 
> I would also note that firefox uses a jemalloc fork (mozjemalloc) and so
> interfaces directly with the OS for memory requests. This allows the browser
> to more carefully tailor their memory allocation needs to the allocator,
> with more apriori information about the allocation patterns you can usually
> do better than a generic allocator.
> 
> The Fedora 25 chromium build does appear to use the system memory allocator,
> and so would be an interesting candidate for analysis if it is indeed
> causing the system to run out of memory.

Chromium/Chrome uses its own tcmalloc fork afaik and I agree with you it does
seems more related to a kernel issues than an userspace one.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]