mimalloc: Crash on Firefox start with mimalloc being ld.so.preload'ed

firefox[7891]: segfault at 28 ip 00007f40c0d8bfa0 sp 00007ffed98afff8 error 4 in libpthread-2.27.so[7f40c0d82000+1a000]

version: 06f8da4218a6e86f0418e249a99faa9957c2ec5f

Description: Ubuntu 18.04.2 LTS GNU C Library (Ubuntu GLIBC 2.27-3ubuntu1) stable release version 2.27.

About this issue

  • Original URL
  • State: closed
  • Created 5 years ago
  • Comments: 19

Most upvoted comments

However, I still think that since Firefox links directly with jemalloc things may not work correctly.

That’s not engineer’s way of thinking. jemalloc isn’t a magic

Ummm… not an “engineer’s way of thinking” huh …

Look, Firefox may use internal jemalloc calls, like xallocx and that will not mix well with a dynamically patched free that uses the mimalloc free. To test properly, we need a build that is not linked statically with jemalloc.

If you have other programs that leak memory I am very interested to get some way to reproduce this locally so I can fix mimalloc.

Best, Daan