Issue 137438 in chromium: "Aw, Snap!" on EVERY page including chrome://version/ and chrome://settings/ unless --single-process

[chro...@googlecode.com]

Status: Unconfirmed
Owner: ----
Labels: OS-Linux Area-Undefined Type-Bug Pri-2

New issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page including
chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Chrome Version : 20.0.1132.43 (Developer Build 0)
OS Linux
WebKit 536.11 (Unknown URL@0)
JavaScript V8 3.10.8.19
Flash 11.2 r202
User Agent Mozilla/5.0 (X11; Linux i686) AppleWebKit/536.11 (KHTML, like
Gecko) Chrome/20.0.1132.43 Safari/536.11
Command Line chromium-browser
--extra-plugin-dir=/usr/lib/nsbrowser/plugins --single-process
--flag-switches-begin --flag-switches-end
Executable Path No such file or directory
Profile Path /home/hkmaly/Gentoo/.config/chromium/Default
OS Version: Gentoo :-)
Other browsers tested: only firefox 3.6 ...
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:

What steps will reproduce the problem?
1. chromium

What is the expected result?
I would expect to see some page, as in version 18 ...

What happens instead?
I see "Aw, Snap!" page instead of everything, including the about:version,
settings, extensions ... I tried clean profile, --disable-extension,
--disable-plugins, --no-sandbox ... but only when tried --single-process
its working. And in single-process, no errors are reported ...

Please provide any additional information below. Attach a screenshot if
possible.

I assume some additional informations would be needed but have no idea
which. ldd?

linux-gate.so.1 => (0xb3f48000)
/usr/lib/gcc/i686-pc-linux-gnu/4.5.3/libstdc++.so.6.0.14
(0xb3e45000)
libpthread.so.0 => /lib/libpthread.so.0 (0xb3e09000)
libdl.so.2 => /lib/libdl.so.2 (0xb3e05000)
libicui18n.so.49 => /usr/lib/libicui18n.so.49 (0xb3be0000)
libicuuc.so.49 => /usr/lib/libicuuc.so.49 (0xb3a6a000)
libicudata.so.49 => /usr/lib/libicudata.so.49 (0xb2949000)
libm.so.6 => /lib/libm.so.6 (0xb2923000)
libX11.so.6 => /usr/lib/libX11.so.6 (0xb2801000)
libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb27f7000)
libXss.so.1 => /usr/lib/libXss.so.1 (0xb27f3000)
libXext.so.6 => /usr/lib/libXext.so.6 (0xb27e2000)
librt.so.1 => /lib/librt.so.1 (0xb27d9000)
libgobject-2.0.so.0 => /usr/lib/libgobject-2.0.so.0 (0xb2796000)
libgthread-2.0.so.0 => /usr/lib/libgthread-2.0.so.0 (0xb2790000)
libglib-2.0.so.0 => /usr/lib/libglib-2.0.so.0 (0xb2680000)
libgtk-x11-2.0.so.0 => /usr/lib/libgtk-x11-2.0.so.0 (0xb22b4000)
libgdk-x11-2.0.so.0 => /usr/lib/libgdk-x11-2.0.so.0 (0xb2219000)
libatk-1.0.so.0 => /usr/lib/libatk-1.0.so.0 (0xb21fc000)
libpangocairo-1.0.so.0 => /usr/lib/libpangocairo-1.0.so.0
(0xb21f0000)
libgdk_pixbuf-2.0.so.0 => /usr/lib/libgdk_pixbuf-2.0.so.0
(0xb21d3000)
libcairo.so.2 => /usr/lib/libcairo.so.2 (0xb20c9000)
libpango-1.0.so.0 => /usr/lib/libpango-1.0.so.0 (0xb2084000)
libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb1ff3000)
libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb1fc2000)
libevent-1.4.so.2 => /usr/lib/libevent-1.4.so.2 (0xb1fa9000)
libsmime3.so => /usr/lib/libsmime3.so (0xb1f82000)
libnssutil3.so => /usr/lib/libnssutil3.so (0xb1f64000)
libnss3.so => /usr/lib/libnss3.so (0xb1e55000)
libplc4.so => /usr/lib/libplc4.so (0xb1e50000)
libnspr4.so => /usr/lib/libnspr4.so (0xb1e18000)
libz.so.1 => /lib/libz.so.1 (0xb1e02000)
libv8.so.3.10.8 => /usr/lib/libv8.so.3.10.8 (0xb1a5a000)
libdbus-1.so.3 => /usr/lib/libdbus-1.so.3 (0xb1a23000)
libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0xb1a1f000)
libpng15.so.15 => /usr/lib/libpng15.so.15 (0xb19f3000)
libjpeg.so.8 => /usr/lib/libjpeg.so.8 (0xb19a0000)
libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0xb199a000)
libasound.so.2 => /usr/lib/libasound.so.2 (0xb18d5000)
libwebp.so.2 => /usr/lib/libwebp.so.2 (0xb189d000)
libxml2.so.2 => /usr/lib/libxml2.so.2 (0xb175f000)
libxslt.so.1 => /usr/lib/libxslt.so.1 (0xb1729000)
libcups.so.2 => /usr/lib/libcups.so.2 (0xb16de000)
libgcrypt.so.11 => /usr/lib/libgcrypt.so.11 (0xb1668000)
libbz2.so.1 => /lib/libbz2.so.1 (0xb1656000)
libexpat.so.1 => /usr/lib/libexpat.so.1 (0xb162f000)
libFLAC.so.8 => /usr/lib/libFLAC.so.8 (0xb15f6000)
libspeex.so.1 => /usr/lib/libspeex.so.1 (0xb15dd000)
libudev.so.0 => /lib/libudev.so.0 (0xb15d0000)
libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/4.3.4/libgcc_s.so.1
(0xb15c1000)
libc.so.6 => /lib/libc.so.6 (0xb1477000)
/lib/ld-linux.so.2 (0xb3f49000)
libxcb.so.1 => /usr/lib/libxcb.so.1 (0xb1459000)
libXau.so.6 => /usr/lib/libXau.so.6 (0xb1455000)
libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0xb144f000)
libffi.so.5 => /usr/lib/libffi.so.5 (0xb1447000)
libgio-2.0.so.0 => /usr/lib/libgio-2.0.so.0 (0xb132e000)
libpangoft2-1.0.so.0 => /usr/lib/libpangoft2-1.0.so.0 (0xb1306000)
libgmodule-2.0.so.0 => /usr/lib/libgmodule-2.0.so.0 (0xb1301000)
libXi.so.6 => /usr/lib/libXi.so.6 (0xb12f2000)
libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0xb12e8000)
libXcursor.so.1 => /usr/lib/libXcursor.so.1 (0xb12dd000)
libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0xb12d9000)
libpixman-1.so.0 => /usr/lib/libpixman-1.so.0 (0xb125a000)
libEGL.so.1 => /usr/lib/libEGL.so.1 (0xb123f000)
libdirectfb-1.4.so.5 => /usr/lib/libdirectfb-1.4.so.5 (0xb11ac000)
libdirect-1.4.so.5 => /usr/lib/libdirect-1.4.so.5 (0xb1195000)
libxcb-shm.so.0 => /usr/lib/libxcb-shm.so.0 (0xb1191000)
libxcb-render.so.0 => /usr/lib/libxcb-render.so.0 (0xb1188000)
libGL.so.1 => /usr/lib/opengl/xorg-x11/lib/libGL.so.1 (0xb112a000)
libplds4.so => /usr/lib/libplds4.so (0xb1125000)
libgnutls.so.26 => /usr/lib/libgnutls.so.26 (0xb1074000)
libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0xb106f000)
libogg.so.0 => /usr/lib/libogg.so.0 (0xb1068000)
libresolv.so.2 => /lib/libresolv.so.2 (0xb1052000)
libX11-xcb.so.1 => /usr/lib/libX11-xcb.so.1 (0xb104f000)
libxcb-dri2.so.0 => /usr/lib/libxcb-dri2.so.0 (0xb104a000)
libxcb-xfixes.so.0 => /usr/lib/libxcb-xfixes.so.0 (0xb1043000)
libdrm.so.2 => /usr/lib/libdrm.so.2 (0xb1037000)
libfusion-1.4.so.5 => /usr/lib/libfusion-1.4.so.5 (0xb102c000)
libglapi.so.0 => /usr/lib/libglapi.so.0 (0xb1008000)
libXxf86vm.so.1 => /usr/lib/libXxf86vm.so.1 (0xb1002000)
libxcb-glx.so.0 => /usr/lib/libxcb-glx.so.0 (0xb0fec000)
libtasn1.so.3 => /usr/lib/libtasn1.so.3 (0xb0fdb000)
libnettle.so.4 => /usr/lib/libnettle.so.4 (0xb0fb0000)
libgmp.so.10 => /usr/lib/libgmp.so.10 (0xb0f4d000)
libhogweed.so.2 => /usr/lib/libhogweed.so.2 (0xb0f3a000)

I'm also attaching the log obtained with --enable-logging --v=1 ...


Attachments:
chrome_debug.log 7.5 KB

[chro...@googlecode.com]

Comment #1 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

When I run the chromium with --disable-seccomp-sandbox, it's Snap again. If
I run it with --disable-seccomp-sandbox --renderer-cmd-prefix='xterm -title
renderer -e gdb --eval-command=run --args' its working. Actually, forget
debugger: chromium --renderer-cmd-prefix='xterm -title renderer -e' works.
Damn, chromium --renderer-cmd-prefix='env' works !

Nothing new on chromium --log-level=0 --enable-logging=stderr --v=1
(and "Aw Snap" again).

[chro...@googlecode.com]

Comment #3 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Noticed following in dmesg:
[ 9299.529069] chrome[15068]: segfault at ca6d3 ip b06ffb7c sp bf81822c
error 4 in libfreebl3.so.12[b06fe000+4d000]
[ 9299.539239] chrome[15074]: segfault at ca6d3 ip b06ffb7c sp bf81822c
error 4 in libfreebl3.so.12[b06fe000+4d000]
[ 9299.550770] chrome[15080]: segfault at ca6d3 ip b06ffb7c sp bf81822c
error 4 in libfreebl3.so.12[b06fe000+4d000]

[chro...@googlecode.com]

Comment #4 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

... I have dev-libs/nss-3.13.1-r2 ...

[chro...@googlecode.com]

Comment #5 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Might be same or similar to Issue 101891 ...

[chro...@googlecode.com]

Comment #6 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Upgrade to dev-libs/nss-3.13.5 didn't helped ...

[chro...@googlecode.com]

Comment #7 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

No change after update to 20.0.1132.57: Still "Aw, Snap!" normally and no
problem with the --renderer-cmd-prefix='env'.

Also the segfaults looks almost same:
[30707.992267] chrome[1048]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30707.998636] chrome[1054]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.007399] chrome[1060]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.010386] chrome[1064]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.022006] chrome[1072]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.035169] chrome[1079]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.061511] chrome[1085]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.066125] chrome[1089]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.071603] chrome[1097]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]
[30708.080846] chrome[1103]: segfault at ca6d3 ip b071991c sp bf8d874c
error 4 in libfreebl3.so.12[b0718000+4d000]

[chro...@googlecode.com]

Comment #9 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

No change after update to oneric - I mean 3.0.0-23-generic-pae #39-Ubuntu
kernel. (Yes, I'm using Gentoo with Ubuntu kernels. Because Ubuntu with
Gentoo kernel wouldn't start.)

[chro...@googlecode.com]

Comment #10 on issue 137438 by the...@chromium.org: "Aw, Snap!" on EVERY

page including chrome://version/ and chrome://settings/ unless
--single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Without a backtrace, there's not much anyone can do to help.
http://wiki.debian.org/Chromium/Debugging

[chro...@googlecode.com]

Comment #11 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

I understand. That's why I'm asking HOW to produce backtrace when the
option recomended to debug the renderer - --renderer-cmd-prefix - simply
causes the crash to NOT appear even if noop like "env" is used instead of
debugger.

[chro...@googlecode.com]

Comment #12 on issue 137438 by the...@chromium.org: "Aw, Snap!" on EVERY

page including chrome://version/ and chrome://settings/ unless
--single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Does this page better explain how to attach to the render processes?
http://code.google.com/p/chromium/wiki/LinuxDebugging#Getting_renderer_subprocesses_into_gdb

[chro...@googlecode.com]

Comment #13 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Seems like (updated?) version of page I already saw. There are three
mentioned possibilities:
1) --renderer-cmd-prefix ; the crash doesn't occur when I use
--renderer-cmd-prefix
2) Connecting to a running renderer. I'm afraid I'm not fast enough for
that. Never catched renderer in the ps list, much less for long enough to
attach debugger to it.
3) enabling core-dumps ; after ulimit -c unlimited, chromium
--allow-sandbox-debugging still didn't left any files matching *core* in
directory it was run from.

[chro...@googlecode.com]

Comment #14 on issue 137438 by the...@chromium.org: "Aw, Snap!" on EVERY

page including chrome://version/ and chrome://settings/ unless
--single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Have you tried Google Chrome to see if it crashes in the same way?

[chro...@googlecode.com]

Comment #15 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Upgraded to newer chrome:
Chromium 21.0.1180.89 (Developer Build 154005)
OS Linux
WebKit 537.1 (Unknown URL@0)
JavaScript V8 3.11.10.20
Flash 11.2 r202
User Agent Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.1 (KHTML, like
Gecko) Chrome/21.0.1180.89 Safari/537.1
Command Line chromium-browser
--extra-plugin-dir=/usr/lib/nsbrowser/plugins
--renderer-cmd-prefix=/usr/bin/env --flag-switches-begin --flag-switches-end

Executable Path No such file or directory
Profile Path /home/hkmaly/Gentoo/.config/chromium/Default

(also some libraries).

No change: Still "Aw, Snap!" normally and no problem with the
--renderer-cmd-prefix='env'.

Google chrome install page recommends to use chromium on Gentoo ... the
chromium on Ubuntu works normally, of course it's version 18. something
where I didn't have problems on Gentoo either ...

[chro...@googlecode.com]

Comment #16 on issue 137438 by the...@chromium.org: "Aw, Snap!" on EVERY

page including chrome://version/ and chrome://settings/ unless
--single-process
http://code.google.com/p/chromium/issues/detail?id=137438

You can probably just download the Google Chrome .deb and extract it to
/opt/google/chrome

[chro...@googlecode.com]

Comment #17 on issue 137438 by kbm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

when i open the google chrome it always shows like aw,snap! it does not
open the web page, settings and any other.

Attachments:
chrome.exe 1.2 MB

[chro...@googlecode.com]

Comment #18 on issue 137438 by kbm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

when i open the google chrome it always shows like aw,snap! it does not

open the web page, settings and any other. what is a remedy for that?

Attachments:
chrome.exe 1.2 MB

[chro...@googlecode.com]

Comment #19 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Ok. I DID downloaded the Google Chrome .deb and extracted it to
/opt/google/chrome (actually, symlinked there). Suprisingly, NO CHANGE: It
goes "Aw, Snap!" on everything including about:version unless I use the
--renderer-cmd-prefix='env' parameter.

Google Chrome 23.0.1271.97 (Official Build 171054)
OS Linux
WebKit 537.11 (@136278)
JavaScript V8 3.13.7.5
Flash 11.5.31.5
User Agent Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.11 (KHTML, like
Gecko) Chrome/23.0.1271.97 Safari/537.11
Command Line ./chrome --renderer-cmd-prefix=/usr/bin/env
--flag-switches-begin --flag-switches-end
Executable Path /mnt/GentooDistfiles/chrome/chrome
Profile Path /home/hkmaly/Gentoo/.config/google-chrome/Default
Variations 853359fa-186f5907
1d3048f1-9de009d0
cd73da34-cf196cb
6214fa18-9e6dc24d
b03ddc1f-2d9ef0cc
4dcb0cd6-d31c4ca1
fe0a565e-595c7724
f9b252d0-fd526c81
ccee547a-766fa2d
f67325bd-b6556a9e
75f7fb7e-766fa2d
24dca50e-837c4893
ca65a9fe-91ac3782
d1a7fd3-4c2186eb
9c097cbc-d00c3f8d
3028188e-b9bbd1b6
2bd5ec9c-275837c2
5a3c10b5-e1cc0f14
244ca1ac-4ad60575
246fb659-bca011b3
f296190c-477de798
4442aae2-d7f6b13c
75f0f0a0-6bdfffe7
e2b18481-6754d7b7
e7e71889-e1cc0f14
980cfc4b-e3130bf3

... so ... did you added some option which actually make possible to debug
this issue meanwhile?

[chro...@googlecode.com]

Comment #20 on issue 137438 by al...@alexx.net: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Ubuntu 10.04.04 (cat /etc/issue Ubuntu 10.04.4 LTS \n \l)
Update manager suggested upgrading chromium and like a fool I
clicked "Upgrade" which should be labelled, "brake every page and even
Tools > Extensions or Settings give will only give an "Aw, Snap" page.)

tail /var/log/apt/history.log

Start-Date: 2013-01-14 10:40:35
Upgrade: chromium-browser-l10n (18.0.1025.168~r134367-0ubuntu0.10.04.1,
23.0.1271.97-0ubuntu0.10.04.1), chromium-codecs-ffmpeg
(18.0.1025.168~r134367-0ubuntu0.10.04.1, 23.0.1271.97-0ubuntu0.10.04.1),
chromium-browser (18.0.1025.168~r134367-0ubuntu0.10.04.1,
23.0.1271.97-0ubuntu0.10.04.1)
End-Date: 2013-01-14 10:41:52

Thanks to this thread I found that:

chromium-browser --single-process

seems to work... for now but ironically Chromium gives an alert at the top
of the page:

"You are using an unsupported command-line flag: --single-process.
Stability and security will suffer."

[chro...@googlecode.com]

Updates:
Labels: nomedia

Comment #21 on issue 137438 by vfedo...@chromium.org: "Aw, Snap!" on EVERY

page including chrome://version/ and chrome://settings/ unless
--single-process
http://code.google.com/p/chromium/issues/detail?id=137438

(No comment was entered for this change.)

[chro...@googlecode.com]

Comment #22 on issue 137438 by the...@chromium.org: "Aw, Snap!" on EVERY

page including chrome://version/ and chrome://settings/ unless
--single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Ok, so it sounds like Google Chrome also crashes. Can you run Google Chrome
with --single-process so it does not crash. Then go to the settings and
turn on crash reporting. Quit the browser and run it without
--single-process on the command line. When it aw snaps, does it upload a
crash report id? The output on the console should look like:

Connecting to clients2.google.com|xxx|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `/dev/fd/3'


[<=>
] 0 --.-K/s
ALPHA_NUMERIC_REPORT_ID_GOES_HERE
XXX `/dev/fd/3' saved

[chro...@googlecode.com]

Comment #23 on issue 137438 by al...@alexx.net: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

google Chrome did not update and is still working perfectly, (just a
problem with chromium.) Then again my version of Chrome is still 18:

Google Chrome 18.0.1025.162 (Official Build 131933)
OS Linux
WebKit 535.19 (@113052)
JavaScript V8 3.8.9.18
Flash 11.2 r202

FYI:
$ chrome2 --single-process
(pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed
(PKIX_PL_Cert_VerifySignature: PKIX_PL_HashTable_Add skipped: entry existed
(PKIX_PL_Cert_VerifySignature: PKIX_PL_HashTable_Add skipped: entry existed
(pkix_CacheCert_Add: PKIX_PL_HashTable_Add for Certs skipped: entry existed
wx=0.345750, wy=0.358550, rx=0.648500, ry=0.330880
gx=0.321210, gy=0.597870, bx=0.155890, by=0.066040

does not crash - I get the pages just as I would expect, (but neither
does "chrome2" on its own.)

[chro...@googlecode.com]

Comment #26 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Whoa. You're right. Update from nss-3.13.5 to nss-3.13.6 solved the problem
(or nspr-4.9.1 to nspr-4.9.2 or possibly only fact that I recompiled the
nss) for both chrome and chromium.

Not sure what to recommend to poor Ubuntu people like al...@alexx.net ...

[chro...@googlecode.com]

Comment #27 on issue 137438 by w...@chromium.org: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

hkmaly: thank you for the info. Here is the stack strace from your crash
report:

Report id 05e6610a5c0da567

Stack Trace (Jump to crashing thread)

Thread 0 *CRASHED* ( SIGSEGV @ 0x000ca6d3 )

0xb14bb91c [libfreebl3.so.12] + 0x0000191c]
0xb14cb630 [libfreebl3.so.12] + 0x00011630]
0xb29ce2c3 [libnspr4.so.9] + 0x0001a2c3]
0xb14cacc9 [libfreebl3.so.12] + 0x00010cc9]
0xb15d8a57 [libsoftokn3.so.12] + 0x00031a57]
0xb15b7049 [libsoftokn3.so.12] + 0x00010049]
0xb15b72fc [libsoftokn3.so.12] + 0x000102fc]
0xb2a69b72 [libnss3.so.12] + 0x00033b72]
0xb2a6a4be [libnss3.so.12] + 0x000344be]
0xb2a7eb69 [libnss3.so.12] + 0x00048b69]
0xb2a7ed26 [libnss3.so.12] + 0x00048d26]
0xb2a4af90 [libnss3.so.12] + 0x00014f90]
0xb2a4b611 [libnss3.so.12] + 0x00015611]
0xb3d72cac [chrome] - crypto/nss_util.cc:450]
crypto::::NSSInitSingleton::NSSInitSingleton
0xb3d734c5 [chrome] - ./base/lazy_instance.h:68] crypto::EnsureNSSInit
0xb3c05b34 [chrome] -
chrome/renderer/chrome_render_process_observer.cc:199]
ChromeRenderProcessObserver::ChromeRenderProcessObserver
0xb3c02bd3 [chrome] -
chrome/renderer/chrome_content_renderer_client.cc:156]
chrome::ChromeContentRendererClient::RenderThreadStarted
0xb5f02341 [chrome] - content/renderer/render_thread_impl.cc:328]
RenderThreadImpl::Init
0xb5f3c6e1 [chrome] - content/renderer/renderer_main.cc:224] RendererMain
0xb3ca0bfc [chrome] - content/app/content_main_runner.cc:391]
content::RunZygote
0xb3ca109c [chrome] - content/app/content_main_runner.cc:723]
content::ContentMainRunnerImpl::Run
0xb3c9f757 [chrome] - content/app/content_main.cc:35] content::ContentMain
0xb373be0a [chrome] - chrome/app/chrome_main.cc:32] ChromeMain
0xb373bdad [chrome] - chrome/app/chrome_exe_main_gtk.cc:31] main
0xb24dbbd4 [libc-2.11.2.so] + 0x00016bd4]
0xb373bcb0 [chrome] + 0x00237cb0]
0xb373bd7f [chrome] + 0x00237d7f]
0xb34f475f [ld-2.11.2.so] + 0x0000f75f]
0xb34fe048 [ld-2.11.2.so] + 0x00019048]

Here is the Bugzilla query for the bugs fixed in NSS 3.13.6:

https://bugzilla.mozilla.org/buglist.cgi?list_id=5403582;resolution=FIXED;classification=Components;query_format=advanced;target_milestone=3.13.6;product=NSS

I compared that list with the source code diffs between NSS 3.13.5 and NSS
3.13.6.
The list is accurate.

None of the bug fixes in that list can explain a crash in libfreebl3.so.12
when NSS is initialized. So I wonder if you didn't compile nss-3.13.5
correctly
the first time. Could you try recompiling nss-3.13.5? Thanks.

[chro...@googlecode.com]

Comment #29 on issue 137438 by al...@alexx.net: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Thank you hkm, chromium-browser --renderer-cmd-prefix='env' works for me.
(I think I'm using nss 3.14.1)

[chro...@googlecode.com]

Comment #33 on issue 137438 by hkm...@gmail.com: "Aw, Snap!" on EVERY page

including chrome://version/ and chrome://settings/ unless --single-process
http://code.google.com/p/chromium/issues/detail?id=137438

Note: I was able to reproduce the issue on different computer. That is:
compile chromium, find out it's doing "Aw, Snap!", upgrade nss, chromium
stopped doing "Aw, Snap!" and started working.

Of course, this time the old nss was nss-3.12.8 compiled in December 2010,
so it's not so surprising it didn't worked.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[chro...@googlecode.com]

Comment #39 on issue 137438 by madelina...@gmail.com: "Aw, Snap!" on EVERY

page including chrome://version/ and chrome://settings/ unless
--single-process

https://code.google.com/p/chromium/issues/detail?id=137438

i'm having this problem now! i can not see one page of my website ... i've
tried everything, including setting up a new account. When will this
problem be fixed?!