> From: [EMAIL PROTECTED]
>...
>
> Yes. And top shows that during the loading process X is taking on the order
> of 80% of processor time, java most of the rest. This is perhaps strange
> because during this period no visible painting related to the applet is
> happening.
I saw that problem too when I had a 486/66 (35 seconds for a minimal
Java window to pop up).
I think something's wrong (or maybe just very inefficient) in the
AWT setup code.
It appeared to me that the AWT code was interrogating the X server about
something (maybe listing all available colors or fonts?), but doing it
horribly inefficiently (since other X applications start without such a
delay).
I also think that since most people (and probably the JDK porters) have
faster machines, the problem isn't noticed by many people so it isn't
fixed (or, if not fixable, listed as a known problem).
Has anyone intercepted the X communications stream to see what the
AWT does when it connects to the X server?
Daniel
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
