Assignee: jhpedemonte → dbradley
Status: UNCONFIRMED → NEW
Component: Java to XPCOM Bridge → XPConnect
Ever confirmed: true
QA Contact: xpcom-bridge → pschwartau
the code to do this currently lives in nsJSContext::InitializeLiveConnectClasses it could be moved to xpconnect i suppose. anyone happen to know how thread friendly java is? reporter: it'd help if you tested this heavily to try to find out if e.g. initializing java on a different thread has any interesting consequences. i suppose it'd be fairly hard to convince gecko to actually try to create its first jscontext off the main thread, the easiest way would probably be a c++ component that in its NSGetModule function created an osnative thread that then tried to instantiate a jscomponent. you'd have to make sure that no jscomponents registered before that c++ component in that session and that no jscomponents were registered to be created at startup before your c++ component tried to do its dirty work. at one point we tried to actively delay java initialization, but i have a feeling that we gave up at some point, i wonder if this would have startup time implications, i guess the answer is probably not much.
I think the global java object is long gone.
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.