Date: Fri, 16 Jun 2017 05:32:22 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 220027] www/firefox: crashes on latest head due to jemalloc update Message-ID: <bug-220027-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D220027 Bug ID: 220027 Summary: www/firefox: crashes on latest head due to jemalloc update Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: gecko@FreeBSD.org Reporter: henry.hu.sh@gmail.com Flags: maintainer-feedback?(gecko@FreeBSD.org) Assignee: gecko@FreeBSD.org jemalloc is updated in base to 5.0 on Jun 15. The result is that firefox crashes minutes after startup, or crashes when doing a measurement in about:memory. The error is: <jemalloc>: jemalloc_ctl.c:1212: Failed assertion: "node->nchildren > 0" The reason is that malloc ctl stats.arenas.0.metadata.allocated is renamed = to stats.arenas.0.internal (see https://github.com/jemalloc/jemalloc/commit/a0dd3a4483e2e72ee80e70424a6522f= 873f2c7ff and https://github.com/jemalloc/jemalloc/commit/751f2c332d91209c5ae3234fa444a20= 850067960), while firefox is still checking the old malloc ctl without checking the ret= urn value of mallctlnametomib. One temporary fix is modifying firefox binary and updating the string. Fire= fox should be patched for this. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220027-21738>