I see this behavior on 8.04 server and with Varnish.
Varnish uses jemalloc. After recent updates, Varnish would not start any
longer. I turns out to be /proc/cpuinfo deadlock in jemalloc.
I am not sure what has changed on the server, but I assume it is related
to recent stable updates.
--
You
** Changed in: firefox
Importance: Unknown = Medium
--
malloc_init deadlock (mozilla jemalloc)
https://bugs.launchpad.net/bugs/333624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
You are not seeing this in our builds per comment above. This is
something you need to track upstream since LP is only for our official
builds.
** Changed in: firefox-3.0 (Ubuntu)
Status: Incomplete = Invalid
--
malloc_init deadlock (mozilla jemalloc)
** Changed in: firefox (Ubuntu)
Sourcepackagename: None = firefox
--
malloc_init deadlock (mozilla jemalloc)
https://bugs.launchpad.net/bugs/333624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
What version of Ubuntu and can you please paste output of
apt-cache policy firefox-3.0
apt-cache policy firefox-3.1
--
malloc_init deadlock (mozilla jemalloc)
https://bugs.launchpad.net/bugs/333624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Do you see this only on firefox-3.1?
** Changed in: firefox-3.0 (Ubuntu)
Sourcepackagename: firefox = firefox-3.0
Status: New = Incomplete
** Bug watch added: Mozilla Bugzilla #474155
https://bugzilla.mozilla.org/show_bug.cgi?id=474155
** Also affects: firefox via
** Changed in: firefox
Status: Unknown = New
--
malloc_init deadlock (mozilla jemalloc)
https://bugs.launchpad.net/bugs/333624
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I see this on the versions of firefox 3.0.x and 3.1.x downloaded from
ftp.mozilla.org. I also see it on the version of 3.1.x I built from
source on the target machine with the debug option, so that I could get
the traceback I posted above.
This doesn't appear to happen with the apt-get version
