chromium-32.0.1700.77 unusable on 8.4 i386

Lena at lena.kiev.ua Lena at lena.kiev.ua
Tue Jan 21 18:38:39 UTC 2014


> From: Ren? Ladan <rene at freebsd.org>

> > On 8.4-RELEASE i386

> These stacktraces are rather useless without debug symbols.
> Try rebuilding Chromium with the DEBUG option on (make config).
> You might have to add WITH_DEBUG=yes to /etc/make.conf (read the fine
> print in bsd.port.mk)

For that my 1467 MB RAM + 768 MB swap proved to be not enough:
build took all day and failed:

[12767/12767] LINK chromeswap_pager: out of swap space
swap_pager_getswapspace(1): failed
Jan 19 21:26:25 bedside kernel: pid 71829 (ld), uid 0, was killed: out of swap space
[12767/12767] LINK chrome
FAILED: /usr/local/bin/clang++33 -B/usr/local/bin -Wl,-z,now -Wl,-z,relro -pthr
...
clang: error: unable to execute command: Killed: 9
clang: error: linker command failed due to signal (use -v to see invocation)

On the second day I added 768 MB more swap on backup HDD - also not enough.
On the third day I added third HDD 8 GB and formatted it entirely as swap:

~ $ swapinfo
Device          1K-blocks     Used    Avail Capacity
/dev/ad0s3b        786432    70336   716096     9%
/dev/ad2s1b       8256992   160044  8096948     2%
Total             9043424   230380  8813044     3%

Under 3 GB swap was used when the final linking hit some other limit:

[12767/12767] LINK chrome
FAILED: /usr/local/bin/clang++33 -B/usr/local/bin -Wl,-z,now -Wl,-z,relro -pthr
...
/usr/local/bin/ld: failed to set dynamic section sizes: Memory exhausted
clang: error: linker command failed with exit code 1 (use -v to see invocation)
ninja: build stopped: subcommand failed.
===> Compilation failed unexpectedly.
Try to set MAKE_JOBS_UNSAFE=yes and rebuild before reporting the failure to
the maintainer.
*** Error code 1
Stop in /usr/ports/www/chromium.


> > Then in chromium-32.0.1700.77 I chose "about Chromium" in menu,
> > clicked the "x" to close the tab - Chromium terminated completely:
> >
> This is a known bug with Chromium 32 (at least under FreeBSD, so I
> might have overlooked something).

I didn't find it on 
http://code.google.com/p/chromium/issues/list?can=2&q=close+tab&sort=-id&colspec=ID+Pri+M+Iteration+ReleaseBlock+Cr+Status+Owner+Summary+OS+Modified&x=m&y=releaseblock&cells=tiles


More information about the freebsd-chromium mailing list