currently we are not using jemalloc in fennec. we should fix this.
Assignee: nobody → pavlov
Flags: wanted-fennec1.0? → wanted-fennec1.0+
Target Milestone: --- → Fennec A1
bsmedberg, ted: since we're using xulrunner-stub as our application piece, we need it to link against jemalloc. I'm not sure how to do this short of making it always link against jemalloc (perhaps that is OK). Thoughts?
as discussed on IRC, the "safe" way to do this is probably to statically link xulrunner-stub against jemalloc (dynamic linking won't work well because you don't actually know where libjemalloc.so lives until the "find libxul" code runs.
Comment on attachment 335102 [details] [diff] [review] ubuntu patch to make jemalloc build statically i'm unsure if this patch is right for linux... do we always want this to be static? i'm not sure what all our different shared/static/libxul/notlibxul/embedding/etc cases are..
Attachment #335102 - Flags: review?(benjamin)
Comment on attachment 335101 [details] [diff] [review] ubuntu's patch to link jemalloc in to xulrunner-stub you want $(call EXPAND_LIBNAME_PATH,jemalloc,$(DEPTH)/memory/jemalloc)
Attachment #335101 - Flags: review?(benjamin) → review-
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → FIXED
If I use firefox-bin not xulrunner to start Firefox on Linux, where does jemalloc live in?
I just did a release build on Linux, I didn't find malloc() implementation in dist/bin binaries.
As I understand it, jemalloc should still be getting linked in via browser/app/Makefile.in for firefox... bsmedberg, is that right?
I think so, and therefore part of firefox-bin itself.
Interesting. nsBrowserApp.cpp doesn't explicit use malloc() function, so linking libjemalloc.a into firefox-bin doesn't have any effect.
We can use MKSHLIB_FORCE_ALL if we want.
Component: General → XULRunner
Product: Fennec → Toolkit
QA Contact: general → xulrunner
Target Milestone: Fennec A1 → ---
You need to log in before you can comment on or make changes to this bug.