4.10Pro......slow, quits often in 10.3.9...?
 

I installed the new 4.10 pro version last night, and I've noticed that the program itself runs much slower than the previous one (more than half the time it's running, my whole system slows down, HD or something starts humming, etc. lots of beachball action). Also, every time I snap the computer out of screen saver mode, the program illegally quits (or has already done so). Any advice?

Jjazz, welcome to the Gnutella forums.

There is here a article which speak of your problem.

What I would do first is to re-install the 10.3.9 Combo over your existing 10.3.9 and see if this not helps

Philippe

I've got exactly the same problem. I've tried all the solutions mentioned in the other threads. Reinstalling the security update, running the Java update, purging the incomplete downloads library, even the one on the Apple site using terminal, all to no avail. I suspect this may be a different problem. The common one seems to occur when installing OSX 10.3.9. I was already running 10.3.9 with no problems at all with Limewire. It was only when I updated to LW 4.10 that the problems started. The application opens ok and to start with everything works fine. Then it gets progressively slower until it can take minutes to respond to a mouse click and eventually Limewire quits. Any other applications running at the same time also slow down.

Same here. I've tried everything, to no avail. I wonder if there's any place to download the previous version? At this point I'm about to give up on Limewire.

I'm quite sure that's a issue with 10.3.9 (Java surely) and 4.10pro.

I have 4.10pro runningon my daughter's G3 running 10.3.8 without any problem

Other things that can be done:

(1) repair permissions
(must be admin)
Launch Applications/Utilities/DiskUtility
On the left pane, select the drive
On the right, select the First Aid (or SOS) tab
Then click on repair permissions and let run; don not worry about messages like " new permissions...."
Quit DiskUtility
Shutdown and reboot

(2) manually run maintenance scripts through Macjanitor
http://personalpages.tds.net/~brian_...acjanitor.html
and use it to run the maintenance scripts
The maintenance scripts are Unix scripts which are automatically ran on your
Mac between 02Am and 04 am..if your Mac is on at this moment.
I can advice you to run, through Macjanitor, the daily script each day, the week script each week, ..and so on

(3) and last but not least the Unix repair function: fsck
To run fsck, you first need to start up your Mac in single-user mode. Here's how:
1. Restart your Mac.
2. Immediately press and hold the Command and "S" keys.
You'll see a bunch of text begin scrolling on your screen. In a few more seconds, you'll see the Unix command line prompt (#).
You're now in single-user mode.

Now that you're at the # prompt, here's how to run fsck:
1. Type: "fsck -y" (that's fsck-space-minus-y).
If the 1st pass says that nothing has to be repaired, try "fsck -fy"
Option "-y" forces a "yes" response to every question of the system, which is very important because answering "no" to a fsck question will stop the process !
Option "-f" forces fsck to chack a system that this command seems to have find "clean"
2. Press Return.
The fsck utility will blast some text onto your screen. If there's damage to your disk, you'll see a message that says:

***** FILE SYSTEM WAS MODIFIED *****

If you see this message--and this is extremely important-- repeat running fsck. It is normal to have to run fsck more than once -- the first run's repairs often uncover additional problems..

When fsck finally reports that no problems were found, and the # prompt reappears:
3. Type: "reboot" to restart,
or type "exit" to start up without rebooting.
4. Press Return.

Your Mac should proceed to start up normally to the login window or the Finder.

Phil

Thanks to Philippe for all the useful tips, particularly MacJanitor which seems like a very useful little application. Unfortunately none of these fixed the problem. I've had a look at what's going on in the activity monitor. Limewire gradually uses up all the available memory until there is about 5M left, at which point everything slows to a crawl. The Virtual Memory size and real memory used by Limewire keep creeping up and the processor and disc activity meters hit the endstops. Looks like a memory leak to me, but whether it's a bug in Limewire or OSX 10.3.9 I've no idea. I'm pretty sure that the problem only started with the update to LW4.10 though. If only I hadn't clicked on that download button. Anyone know how I can go back to an earlier version of Limewire?

Deano

Tried the latest JUM version last night (clutching at straws here) but it's no better.

Same problem here
 

Just wanted to note that I have exactly the same symptoms as Deano777. The problem only occured after going to Pro4.10. This is not the Java problem. Any other ideas would be greatly appreciated. When I tried to contact Limewire Pro support the link does not work.

Greg

Only A Hobo was suffering a similar problem. As a last resort I suggested trying the Jum CVS nightly build & it seemed to work for him. It might not work for everybody, but if you check Jum's nightly builds, there's more than one to try. http://www.mager.org/LimeWire/ Jum's builds require no installation, just drag & drop from the dmg. One of Jum's build's might just do the trick. I think his last one was 4.10.2 jum20060105230004 But you need to click on the "nightly" builds link to find them.

BTW I would also recommend the Java reinstall using the "Offline" standalone installer, but this one: http://www.apple.com/downloads/macos...update142.html
If it won't let you install it, then double-click the harddrive icon, open the Library, open the Receipts folder, then find the file: Java142Update2.pkg, delete it and try again. Receipts folder sample image

I would also recommend a SAFE boot, ie: rebooting whilst holding down the SHIFT key until you see the message booted in safe mode. Then open Disk Utility & repair permissions. Then reboot normally. Do this before using LW again & after reinstalling java.

It might also be worth deleting your LW preferences. Search for limewire (in prefs folder) using Search/Find & delete it. Oh I forgot to mention, when doing this search, select extra search option & choose Visibility -> show visible & invisible items. LW 4.10 has its preferences folder in a new location depending upon whether you've deleted the prefs folder since updating. In any case, it'll prolly be wise to delete whatever LW prefs you can find. ;)

Nice timing OAH lol :D

Yes mac os has lots of invisible files. Lots!!! I have a utility or 2 which can convert an entire partition or folder's contents to show all invisible files. You'd be surprised. But it comes in handy sometimes when ... oh ... should keep quiet. lol :D Forum rules.