Comment #14 on issue 13929 by willc...@chromium.org: Crash in
NSS_InitReadWrite on Ubuntu Hardy
http://code.google.com/p/chromium/issues/detail?id=13929
Note that this is only a bug in chrome on Ubuntu Hardy. Ubuntu Jaunty uses
a newer
version of NSPR that fixes this bug.
--
You received t
Updates:
Status: Started
Owner: willc...@chromium.org
Cc: -willc...@chromium.org
Comment #13 on issue 13929 by willc...@chromium.org: Crash in
NSS_InitReadWrite on Ubuntu Hardy
http://code.google.com/p/chromium/issues/detail?id=13929
Aha! We think we've figured this ou
Updates:
Owner: ---
Labels: -Pri-1 Pri-0
Comment #8 on issue 13929 by e...@chromium.org: Crash in NSS_InitReadWrite
on Ubuntu Hardy
http://code.google.com/p/chromium/issues/detail?id=13929
Do we have a handle on why this is happening?
Status:Available + Owner set is a confusin
Comment #7 on issue 13929 by daniel.r.kegel: Crash in NSS_InitReadWrite on
Ubuntu Hardy
http://code.google.com/p/chromium/issues/detail?id=13929
I saw a similar problem on the valgrind bots today:
http://build.chromium.org/buildbot/waterfall.fyi/builders/Webkit%20Linux%20(valgrind%
20layout)/
