Welcome to the MacNN Forums.

andreas_g4 · Sep 21, 2003, 04:46 AM

See:

After any rebbot, java is taking almost 100% of CPU time. This lasts for about one minute, then it's ok. Why does this happen? I have installed the latest Java update, of course.

Gul Banana · Sep 21, 2003, 06:41 AM

The VM is caching shared objects.

andreas_g4 · Sep 21, 2003, 06:58 AM

Originally posted by Gul Banana:
The VM is caching shared objects.

Would you be so kind to explain that to me? Is this always like that?

Arkham_c · Sep 21, 2003, 09:06 AM

Originally posted by andreas_g4:
Would you be so kind to explain that to me? Is this always like that?

I can't find the URL, but the basic gist is that Apple added some extensions to Java that preload some shared libraries and objects so that they can be used between java launches without loading them every time. Apple submitted these changes back to Sun for inclusion in a future release of java.

DaGuy · Sep 21, 2003, 10:05 AM

What java software are you running?

Did you try killing the java process and restarting it?

How long until the behavior reappears?

Try starting a different Java process, is the CPU hogging behavior still present?

EDITORIAL SECTION
It seems to me that your java app is not up to snuff. You may consider looking for a substitute or killing and restarting the process every so often, when it becomes a real perfomance burden on the CPU.

This is probably too much work unless it's something very important to you. My guess at this point is, that you are running some crappy Java software which is holding onto resources that steadily consume CPU.

andreas_g4 · Sep 21, 2003, 02:16 PM

Originally posted by DaGuy:
This is probably too much work unless it's something very important to you. My guess at this point is, that you are running some crappy Java software which is holding onto resources that steadily consume CPU.

As I said, it occures right after rebooting, with no apps started by me. It's a system-started java process and stops eating after a minute or so. I was just curious.

Gul Banana · Sep 21, 2003, 06:58 PM

It is perfectly normal, it happens to everyone, and killing the process would just result in it starting back up again. What machine do you have? Ironically, the faster it starts up, the longer it will spend after it seems to have finished booting running background processes that are really still initialization stuff.