But firefox needs to use the NSS/NSPR delivered by JES team. This is required by ARC right? So we won't ship firefox with its own NSS/NSPR.
Alan Coopersmith wrote: > brian.lu wrote: >> Hi, experts, >> >> We met a problem when tuning firefox startup performance. The issue is: >> NSPR shared library (which is used by Firefox) exports an interface >> (a function name) to the applications (like Firefox). Applications >> can provide a implementation of that function to override some >> function provided by NSPR. Firefox doesn't use that interface. I.e. >> it doesn't define that symbol. >> >> But every time, when firefox starts, NSPR lookups that symbol by >> using dlsym(). That takes some time and fails finally. We can't >> modify the NSPR codes >> because it is not part of firefox code base. > > But firefox ships it's own copy of NSPR, so isn't it effectively part of > the firefox code base? >
