If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

MRJ Plugin printfs to console in release builds

RESOLVED INCOMPLETE

Status

Plugins Graveyard
Java (Java Embedding Plugin)
RESOLVED INCOMPLETE
12 years ago
a year ago

People

(Reporter: Simon Fraser, Unassigned)

Tracking

Details

(Reporter)

Description

12 years ago
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?
(Reporter)

Updated

12 years ago
Summary: MRJ Plugin prints in optimized builds → MRJ Plugin printfs to console in optimized builds
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?

(Reporter)

Comment 2

12 years ago
(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?

Comment 4

12 years ago
Optimized, as in any non-debug build.
> Optimized, as in any non-debug build.

OK.  Thanks.

(Reporter)

Comment 6

12 years ago
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.
Component: Plug-ins → Java Embedding Plugin
QA Contact: plugins → java.jep
Duplicate of this bug: 460121

Comment 8

9 years ago
Clarifying summary wording to make it obvious what's meant here.
Hardware: Macintosh → All
Summary: MRJ Plugin printfs to console in optimized builds → MRJ Plugin printfs to console in release builds

Updated

8 years ago
Component: Java Embedding Plugin → Java (Java Embedding Plugin)
Product: Core → Plugins
Version: Trunk → unspecified
The MRJPlugin and JEP are long gone.
Assignee: smichaud → nobody
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
(Assignee)

Updated

a year ago
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.