Date: Mon, 04 Jun 2018 17:04:30 +0000 From: bugzilla-noreply@freebsd.org To: threads@FreeBSD.org Subject: [Bug 220767] lang/beignet: hangs if consumer is not linked against libpthread after jemalloc 5.0.0 update Message-ID: <bug-220767-13406-zdIJ4BeNvG@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-220767-13406@https.bugs.freebsd.org/bugzilla/> References: <bug-220767-13406@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220767 --- Comment #10 from Alexey Dokuchaev <danfe@FreeBSD.org> --- (In reply to Jason Evans from comment #6) > I don't have any specific ideas as to why this is happening. Bootstrapping > jemalloc on FreeBSD is really tricky, because pthreads mutexes use malloc, > and jemalloc has to jump through hoops to initialize its mutexes in multiple > phases [...] OK, but can you think of anything that had *changed* between 5.0.0 vs 4.5.0 in that area that could've caused this regression? Looks like some software was working fine for years (that is the case at least for Quake2) until 5.0.0 hit the tree, so I want to know if 5.0.0 had revealed a bug in those programs, or rather introduced a bug into itself? -- You are receiving this mail because: You are on the CC list for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-220767-13406-zdIJ4BeNvG>