Enable jemalloc by default on Linux

RESOLVED FIXED in mozilla1.9beta4

Status

defect
RESOLVED FIXED
12 years ago
Last year

People

(Reporter: pavlov, Assigned: pavlov)

Tracking

Trunk
mozilla1.9beta4
x86
Linux
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments)

jemalloc. wee.
OS: Windows XP → Linux
Version: unspecified → Trunk
Attachment #302879 - Flags: review+
Flags: blocking1.9+
OS: Linux → Windows XP
Version: Trunk → unspecified
checked in
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla1.9beta4
Version: unspecified → Trunk
Attachment #302939 - Flags: review? → review+
OS: Windows XP → Linux
Comment on attachment 302939 [details] [diff] [review]
disable jemalloc if trace-malloc is on

Seems better not to silently disable -- I'd change the default of MOZ_MEMORY based on trace-malloc, but make explicitly enabling both give an error...
My build is trying to link in a static libjemalloc.a, but only the shared libjemalloc.so is being built.

gmake[5]: *** No rule to make target `../../staticlib/libjemalloc.a', needed by `firefox-bin'.  Stop.
Depends on: 417163
r=/sr=/a=pavlov on irc

Checking in Makefile.in;
/cvsroot/mozilla/memory/jemalloc/Makefile.in,v  <--  Makefile.in
new revision: 1.4; previous revision: 1.3
done
Attachment #302998 - Flags: superreview+
Attachment #302998 - Flags: review+
Duplicate of this bug: 417172
That's some 20ms Ts regression :(
This broke 64bit-Linux/Fedora7 builds, at least debug versions.
No problems in compilation, but when trying to start FF, I get the following error:
"Error: in (function call): procedure or syntax required but got: Error: fatal: looped fatal error"

I don't even know which library prints that out. Clobbering didn't help, until
I removed MOZ_MEMORY=1 from configure script.
(In reply to comment #9)
> I removed MOZ_MEMORY=1 from configure script.
--disable-jemalloc has ofc the same effect.
I cannot start Firefox trunk build without --disable-jemalloc if GTK_IM_MODULE=uim.
If it is GTK_IM_MODULE=xim, I can start fx. Should I file a new bug? And which component is suitable if I will file?
file a new bug, put stacks/etc in it.
Depends on: 418016
Depends on: 423279
Depends on: 466388
Product: Core → Firefox Build System
You need to log in before you can comment on or make changes to this bug.