Bug#647992: chromium crashes

[Jonathan Nieder]

Jonathan Nieder wrote:

> chromium --temp-profile --renderer-cmd-prefix='xterm -e'::
> 	Renderer doesn't die.
>
> chromium --temp-profile --renderer-cmd-prefix=''::
> 	Renderer dies, chrome stays alive --- no backtrace.
>
> Which makes sense: as the upstream LinuxDebugging doc says,

More notes!  The renderer request is sent to and successfully served
by the zygote[1]:

| forking request "/proc/self/exe" "--type=renderer" "--lang=en-US" "--force-fieldtest=ConnCountImpact/conn_count_6/ConnnectBackupJobs/ConnectBackupJobsEnabled/DnsImpact/default_enabled_prefetch/DnsParallelism/parallel_default/GlobalSdch/global_enable_sdch/IdleSktToImpact/idle_timeout_10/Prefetch/ContentPrefetchPrerender2/ProxyConnectionImpact/proxy_connections_32/SpdyCwnd/cwndMin16/SpdyImpact/npn_with_spdy/SuggestHostPrefix/Default_Prefix/WarmSocketImpact/warmest_socket/" "--disable-client-side-phishing-detection" "--enable-click-to-play" "--channel=547.0x7fcb143bc000.1339080197" 
| this is it --- sending requset
| reply is pid 566

Successfully, except that the forked child dies.

Renderer doesn't die with "--no-sandbox", alas.  Next attempt:

 $ chromium --temp-profile --zygote-cmd-prefix='\
/usr/bin/xterm -title zygote -e gdb --eval-command=run --args' \
	--log-level=0 --enable-logging=stderr --v=1
 [1507:1507:243277707209:FATAL:zygote_host_linux.cc(198)] Check failed: pid_ > 0. Did not find zygote process (using sandbox binary /usr/lib/chromium/chromium-sandbox)
 Aborted (core dumped)

Maybe gdb takes too long to load the debugging symbols and the
"chromium-sandbox --find-inode" is not able to find it.

[1] http://code.google.com/p/chromium/wiki/LinuxZygote

$ uname -a
Linux elie 3.1.0-1-amd64 #1 SMP Thu Nov 3 19:35:59 UTC 2011 x86_64 GNU/Linux