Broad searches that receive many results can slow you down to a large extent.

Becoming an Ultrapeer can consume a lot of your resources. Check the Connections tab.

Thanks
-greg

No good, Greg.

Your answer does NOT address the problem.

If my computer were acting as an Ultrapeer of if I were conducting a board search [which I don't], I would see the CPU load creditted to LimeWire, not Window Manager.

At this very moment, with no searches in progress, LimeWire is holding 15% of the CPU and Window Manager 70%

This is clearly a LimeWire bug.

Janet.

Hi, I am the original post of this thread ( previously "unregistered"). So just continuing, now registered as "digidan". thanks

Thanks Janet for folloowing through. You are obviously more advanced than I in these matters. I appreciate it.

Downloading in, or using of Limewire isn't the problem. All I have to do is launch Limewire, and everything else almost stops naer dead, immediately. As a matter of fact, trying to launch any other program while Limewire is running is impossible too.

Is it possible that my G4/400 processor could be an issue?

I am using 10.2.2, and have been updating my other software as anything becomes available. Could it be another software conflict?

Thanks for the continued attempts to solve this.

Dan

Dan,

Look at the yesterday's post from CptChipJew. He claims to have solved the problem.

I haven't tried his solution yet -- I probably won't have time today, but I'll get back to you when I know something more.

Try my solution. It works. I posted it yesterday. Reply with your results to it so I can get an idea of why it works.

This is happening not because of searching, or because of ultrapeer technology (greg), but because LimeWires loading program is doing something really stupidly wrong. So, the solution is to load the file yourself.

I've just noticed one possible problem that will result in system slowdown.

Anytime I have Limewire open with its window showing and in the background, and have another window in front of its window, the "Window Manager" process jumps to a steady 50%-60% %CPU usage. (This is on a Yikes! G4 400@450 w/ 1GB RAM). Window Manager is the process that's responsible for creating and updating the image that's shown on your screen.

Seems like something funky is going on with window refreshing. It could be a Java thing and not even be Limewire's fault. It looks like this is the problem that I've been experiencing for quite some time. It makes sense now, that the Window Manager process is hogging all the CPU cycles. That's why I'd never get the 1 second updates while running "top" in the terminal. Top may well have taken the sample but Window Manager was too busy with other stuff to show me. Running Quartz Debug (one of the Developer Tools applications) confirms this and shows Limewire's window and the layered window constantly being updated.

My recommendation is to keep Limewire's window in front of everything else, and when you need to switch to another application (the Finder for example) hit Command+H to hide Limewire's window. Then to switch back to Limewire, click its icon in the dock.

Hope this helps....

Well you found something mDouma46! I tried hiding Limewire and sure enough I have control back of the system. I don't understand why, since I am not technically inclined, but for now, at least I have a workaround. THANKS!

Hopefully some real fix will come along soon.

Dan :)

Dan & Chip,

I've tried Chip's solution and, so far, it's looking good.

First, the crazy behavor of Window Manager seems to have disappeared.

However, LimeWire is now claiming much more of the CPU: between 30 to 80% of my G4/400MHz.

BUT, LimeWire is no longer dominating the system. Just now I started up LimeWire, then Process Viewer, Netscape, AppleWorks, and Explorer and all were running normally.

This morning, before trying Chip's terminal trick, I couldn't get a single other application to run with LimeWire.

This is clearly a programming bug -- how does one file a bug report for this system?

Janus-

You're definitely 10.2.1 and not 10.2.2, right? I've been unable to reproduce any of these issues on 10.2.1, and many of the other users who have had problems have had issues with 10.2.2.

Thanks.

Adam,

Yes, 10.2.1

I sent my reply to Dan & Chip when I was still running LimeWire 2.7.13

Since them I've installed 2.8.0 Beta. I've posted my coments on the Beta in another thread. I my opinion its unuseable under OS X in its current state.