[Bug 422928] Re: Crashes in libnss3.so or libnss3.so.1d around the nss package update on 2009-08-04

[Wan-Teh Chang]

On Sat, Sep 26, 2009 at 3:49 AM, Alexander Sack <asac at ubuntu.com> wrote:
> Hi Wah-Teh,
>
> (feel free to assign me for future bugs directly to get my instant
> attention.)
>
> Is there anything we should do here? Maybe chromium doesn't like if an
> initially loaded lib goes away? for instance chrome has a multi process
> approach. could that cause issues when underlying libs are updated while
> the top process is running?

Hi Alexander,

I just wanted to let you know about this bug and
see if other products have reported a similar issue
during a library upgrade.  Please feel free to mark
the bug invalid.

Chromium has a single executable program that
is used for both the browser process (the top
process) and the renderer processes.  I believe
NSS is only used in the browser process (for
SSL and certificate verification).  NSS functions
are not used until the browser does the first
HTTPS request.

Could something go wrong if Chromium starts,
the NSS library gets updated, and then Chromium
does the first HTTPS request?

Wan-Teh

-- 
Crashes in libnss3.so or libnss3.so.1d around the nss package update on 2009-08-04
https://bugs.launchpad.net/bugs/422928
You received this bug notification because you are a member of Mozilla
Bugs, which is subscribed to nss in ubuntu.