On Mar 24, 2011, at 9:54 AM, AJ Gregory wrote:
> So looks like Chrome and FireFox 4 are using the new Plugin to run
> applets in their own process.
> Couple of questions/issues:
> 1. Is the default heap for the new java process larger than the 96MB
> max for the old in-process applet?
Plugin2 does not explicitly set a heap size for the spawned JVM. Currently, the default max heap size looks like 126M for a 64-bit process (as I've measured it with JVisualVM), but I can get a more authoritative answer if necessary.
> 2. Does this applet param work to increase heap size like it does in windows?
> <param name="java_arguments" value="-Xmx256m">
It should. :-)
> 3. Also looks like anti-aliasing isn't working. The text which shows
> in the overlay as you hover the mouse in this player is anti-aliased
> in FireFox 3.6 but not in FireFox 4 or Chrome. Is this a known issue?
We are aware of a discrepancy in the text anti-aliasing defaults, and we believe we have a fix for it. Please stay tuned for our next developer preview.
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden