Limewire Quits

This is weird. I know about LW, I shouldn't be having problems, but I am.

All of a sudden, starting about two days ago, whenever I leave LW on for an extended period of time, it quits. I don't know why. I mean, I'm supposed to, and I do, leave it on for periods of days, to get established in the network, share, and be a UP. But all of a sudden, it's been quitting. I uninstalled the program, deleted preferences, everything, and reinstalled it, the problem is still there. I haven't modified my computer. Any ideas? I'm prolly going to run norton later, maybe some file is corrupted or something.

The problem still exists. Whenever I leave my computer for an extended period of time (more than say, 15 minutes), I return to find that LW has crashed. I reinstalled it after uninstalling the old one. The problem remains. Any ideas?

A Mac user with Norton/Symantec software on his machine? Now that's something I would strongly advise against. Most of the admittedly anecdotal evidence is that these packages inhibit the performance of Macs. There are better ways of protecting your machine depending on your need.

And, as a suggested explanation for the quitting phenomenon, I have seen the re-emergence of the problem since upgrading to OS10.2.6 having enjoyed continuous operation under OS10.2.5. Probably just coincidence?

Well, it's nice to see I'm not the only one. Hopefully with 10.3 (let's pray to god it'll be free) or the next LW version, it'll be fixed.

Ok but what do i do when limewire quits before it even starts up? I click on th icon in the dock, it bounces, a little black triangle comes...then goes in a matter of seconds

Hmm...try reinstalling it.

ive tried reinstaling it.

Try removing the dock icon, and going to the application directly. If that works, add Limewire to the dock manually, it may be that Limewire did not properly install the dock alias.

no luck

Limewire worked fine until I upgraded to limewire pro 3.3. Since then it has repeatedly quit after operating from 1-15 minutes. Today I upgraded to 3.3.5 and the problem is still there. Any ideas?