ISHIKAWA, Chiaki
unread,Mar 29, 2013, 10:26:55 AM3/29/13You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to
Lately, for like one week, after refreshing the source code of comm-central (and got the
new built system working),
I have seen memory exhaustion during the final link phase of
debug build of TB during libxul.so creation or something.
The error messages when the build aborts is like this:
[...]
INPUT("../../media/webvtt/cuetext.o")
INPUT("../../media/webvtt/error.o")
INPUT("../../media/webvtt/lexer.o")
INPUT("../../media/webvtt/node.o")
INPUT("../../media/webvtt/parser.o")
INPUT("../../media/webvtt/string.o")
libxul.so: warning: Not enough memory to sort relocations
/usr/bin/ld: final link failed: Memory exhausted
collect2: error: ld returned 1 exit status
make[5]: *** [libxul.so] Error 1
make[4]: *** [libs_tier_platform] Error 2
make[3]: *** [tier_platform] Error 2
make[2]: *** [default] Error 2
make[1]: *** [default] Error 2
make: *** [build] Error 2
I was so taken aback, but found that I can invoke top-level make again, and THEN,
the build proceeds as if nothing has happened!?
(So whatever ld was doing, "sort relocations" (?), may not be that
vital/essential to the linux 32 build.)
Not only that there was a time when the message was printed, but, the build was not aborted and proceeded:
e.g.,
[ ... ]
./test_updatecheck.js
./test_blocklist_regexp.js
/COMM-CENTRAL/comm-central/mail/components/im/all-im.js: WARNING: no preprocessor directives found
libxul.so: warning: Not enough memory to sort relocations
mochijar/
mochijar/chrome.manifes
[...]
So it could be that the ld process may be killed by OOM killer or something.
Just wanted to give early warning so that if this problem gets fatal and get in the way
[well, it has already gotten in the way, but issueing top-level make the second time
solves the problem, I am not bothering with it so much],
somebody may have already thought about mitigation plan.
Maybe "sort relocation" is a nicety to make the subsequent linking, etc. a little more efficient, but
not essential.
TIA
PS: I *THINK* the build is working the second time when I issue the top-level make.
But it may be that the libxul.so or something is not quite well updated (?).
I am debugging an issue by sprinkling printf statements to keep track
of some variables, but
I am not sure if all the printf statements spread across a few source files
are reflected in the output. Hmm...