Comment #17 on issue 4609 by bugdro...@chromium.org: NSS_Shutdown reports
leaks
http://code.google.com/p/chromium/issues/detail?id=4609
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=revrevision=22394
Updates:
Status: Assigned
Labels: -Pri-2 Pri-3
Comment #12 on issue 4609 by e...@chromium.org: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
Wan-Teh, any thoughts?
--
You received this message because you are listed in the owner
or CC fields
Comment #13 on issue 4609 by w...@chromium.org: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
evan: I agree that this bug should have priority 3. Usually this kind
of object leaks at NSS shutdown is harmless unless the application will
immediately
Comment #14 on issue 4609 by e...@chromium.org: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
Currently we print a scary-looking message. Should it be removed? What is
the point
of calling this shutdown (and PR_Shutdown, which is in the same situation),
Comment #15 on issue 4609 by daniel.r.kegel: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
Yes. The message should go.
One reason to call the shutdown functions is to make finding leaks easier...
--
You received this message because you are listed in the
Comment #16 on issue 4609 by e...@chromium.org: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
http://codereview.chromium.org/159836
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this
Comment #4 on issue 4609 by aerickson: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
I just experienced this also.
[13468:13468:244967392994:ERROR:/usr/local/google/chrome/home/chrome-svn/tarball/chromium/src/base/nss_init.cc(79)]
NSS_Shutdown failed, leak?
Comment #3 on issue 4609 by de...@chromium.org: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
I am seeing this now on Chrome.
base/nss_init.cc(79)] NSS_Shutdown failed, leak? See
http://code.google.com/p/chromium/issues/detail?id=4609
Comment #2 on issue 4609 by phajdan.jr: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
I tried reproducing this behavior on Linux, but NSS_Shutdown returned
success. Is
this fixed, or am I doing something differently than you?
--
You received this message
Updates:
Cc: [EMAIL PROTECTED]
Comment #1 on issue 4609 by [EMAIL PROTECTED]: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of
Issue 4609: NSS_Shutdown reports leaks
http://code.google.com/p/chromium/issues/detail?id=4609
New issue report by [EMAIL PROTECTED]:
In base/nss_init.cc, there is a call at shutdown time to
NSS_Shutdown. This returns failure if there are any leaks.
This happens currently when running
11 matches
Mail list logo
