I get this in the console every time I run Camino now: ### MRJPlugin: getPluginBundle() here. ### ### MRJPlugin: CFBundleGetBundleWithIdentifier() succeeded. ### ### MRJPlugin: CFURLGetFSRef() succeeded. ### First, why are we loading the MRJ Plugin on startup? Second, why is this printed at all?
The MRJ Plugin JEP (and before that the MRJ Plugin) has always displayed this when it's launched. It's sort of a quiet splash screen, and is actually beneficial -- if it hadn't been displayed, how would you have known that Mozilla.org browsers had returned to launching the x-java-vm/x-java-applet MIME type handler on startup? :-) That the x-java-applet MIME type handler is being launched on startup is (at least) unexpected behavior, though. All Mozilla-family browsers used to do this before the fix for bug 128366 was landed on the trunk (December 2004), and Camino 0.8.4 and Firefox 1.0.7 still do. But I've never seen this happen with a (post 12-2004) trunk or 1.8-branch build. What are the "optimized builds", and where can I find one?
(In reply to comment #1) > What are the "optimized builds", and where can I find one? http://www.mozilla.org/developer/#builds
>> What are the "optimized builds", and where can I find one? > >http://www.mozilla.org/developer/#builds So by "optimized builds" you mean the nightlies?
Optimized, as in any non-debug build.
> Optimized, as in any non-debug build. OK. Thanks.
OK, I guess this plugin loading only happens during xpcom component registration, so it's not such a problem. Oddly, the startup perf test shows this printf every time, suggesting that it's not a good measure of normal startup performance.
Clarifying summary wording to make it obvious what's meant here.
The MRJPlugin and JEP are long gone.