Comment #7 on issue 20819 by [email protected]: Handle NSS initialization failure gracefully
http://code.google.com/p/chromium/issues/detail?id=20819
My commit r25630 fixed the most important part of this bug. The remaining work is 1. pop up an informational dialog if we had to initialize NSS without databases, and 2. make sure our SSL and crypto functions fail gracefully rather than crashing if we can't initialize NSS without databases either. #1 is useful but low priority, so we can postpone until some user requests it. #2 could be an intrusive change. Since it's extremely unlikely for NSS_NoDB_Init() to fail, I'm fine with not doing #2. (We don't protect for Winsock initialization failure either.) -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings
-- Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs
