Closed
Bug 451193
Opened 16 years ago
Closed 16 years ago
use jemalloc in fennec for maemo
Categories
(Toolkit Graveyard :: XULRunner, defect, P1)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dougt, Assigned: pavlov)
References
Details
Attachments
(2 files, 1 obsolete file)
726 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
933 bytes,
patch
|
benjamin
:
review+
|
Details | Diff | Splinter Review |
currently we are not using jemalloc in fennec. we should fix this.
Reporter | ||
Updated•16 years ago
|
Flags: wanted-fennec1.0?
Assignee | ||
Updated•16 years ago
|
Assignee: nobody → pavlov
Flags: wanted-fennec1.0? → wanted-fennec1.0+
Target Milestone: --- → Fennec A1
Assignee | ||
Comment 1•16 years ago
|
||
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?
Comment 2•16 years ago
|
||
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.
Assignee | ||
Comment 3•16 years ago
|
||
Assignee | ||
Comment 4•16 years ago
|
||
Assignee | ||
Updated•16 years ago
|
Attachment #335101 -
Flags: review?(benjamin)
Assignee | ||
Comment 5•16 years ago
|
||
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)
Updated•16 years ago
|
Attachment #335102 -
Flags: review?(benjamin) → review+
Comment 6•16 years ago
|
||
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-
Assignee | ||
Updated•16 years ago
|
Priority: -- → P1
Assignee | ||
Comment 7•16 years ago
|
||
Attachment #335101 -
Attachment is obsolete: true
Attachment #335583 -
Flags: review?(benjamin)
Updated•16 years ago
|
Attachment #335583 -
Flags: review?(benjamin) → review+
Assignee | ||
Updated•16 years ago
|
Status: NEW → RESOLVED
Closed: 16 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.
Assignee | ||
Comment 10•16 years ago
|
||
As I understand it, jemalloc should still be getting linked in via browser/app/Makefile.in for firefox... bsmedberg, is that right?
Comment 11•16 years ago
|
||
I think so, and therefore part of firefox-bin itself.
Comment 12•16 years ago
|
||
Interesting. nsBrowserApp.cpp doesn't explicit use malloc() function, so linking libjemalloc.a into firefox-bin doesn't have any effect.
Comment 13•16 years ago
|
||
We can use MKSHLIB_FORCE_ALL if we want.
Updated•16 years ago
|
Component: General → XULRunner
Product: Fennec → Toolkit
QA Contact: general → xulrunner
Target Milestone: Fennec A1 → ---
Updated•8 years ago
|
Product: Toolkit → Toolkit Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•