I have been trying to run LimeWire on 10.2 for a couple weeks now. (I was running c115, the last developer release) I am not using "Pro", as I wanted to get this working first.

Here are a list of problems:

Latest version doesn't connect - as noted in other discussions here, it can be made to work by pasting in new connection addresses.

Frequent crashes - OS X doesnt crash, but Limewire hangs a couple times a day. It happens most frequently after a rash of searches. I can't quite pin it down, though, but do a bunch of searches, try to download 50+ (unsuccessful) files, and it almost always hangs.

Another indicator of a hang in progress, is the GUI gets very very slow, and then after a few more minutes working, it quits.

Maybe Limewire doesnt grab enough memory?

Performance is horrible, but I don't know it is the network, or Limewire. I have spoken to people who have no problems getting consistent, reliable downloads, almost napster days like, but I can rarely find hosts wo can serve a file in one piece, or at decent consistent speeds. i have a permanent, fast connection, so the problem is unlikely on my side.
bugs:
1. When doing more than 1 row of searches, the upper row of searches cannot be deleted/canceled.
2. Force Resume does not appear to do anything unless the status is in other than "requery sent, waiting...". Would think it would force a resend, restarting the queue.
3. It looks as if when there are multiple sources for a file, that downloads are attempted from all. But it seems if one of those servers is busy, that the download doesn't proceed. Not sure about this, but sometimes multiple hosts will download more consistently, others, not at all. I cannot figure out why.
4. This will clear up when the crashes are addressed, but after about 10% of crashes, Limewire does not find the "in progress" downloads in the queue in the lower window. I imagine the list gets corrupted.
5. Queued items slow performance noticeably. For instance, if I try to download 20 items in the download list, and only 2 or 3 are actively downloading, performance still slows, and even when those initiated files complete, older queued items do not restart. their host is online, as if a download stops, sometimes you can kill download, then restart it, and it will download.
6. When running Colsole, I get the following error in the log: Sep 2 10:49:59 localhost /Applications/LimeWire/LimeWire.app/Contents/MacOS/LimeWire: kCGErrorFailure : CGTranslateCTM is obsolete; use CGContextTranslateCTM instead. (I do not know what this means, but seems like an obsolete API is being called)
7. I think this is a bug, but it may be I don't understand this well enough.. When I am able to "Browse Host", and view the files contained, I often find "multiple hosts" there. Not sure what is going on, but I expected all files to be served from the same machine/host.

GUI Issues:
Cannot do searches (as far as I can tell) using "quotes" to restrict searches to ONLY exact phrases. Such as "killer instinct" still finds instances of both words.

"Quality" is not defined well, and there seems to be no relationship between a working and non-working 4 star site. Three stars seem the same. Perhaps a note in the documentation about this?

The "connections workaround" is temporary, of course, but when I paste in a new connection, I would expect it to survie a quit. Else, hope you resolve this soon, so it is not a problem! ;-)

WishList seems to do nothing? I have to look it up and see if there is a way to use it, but at best the interface is lacking for this feature, and possibly it just doesnt work.

Feature ideas:
A "speed test" capability would be nice - have a "check connection" when a connection claims to be a t3/t1, or cable/DSL line, or even check that modems are not "underreporting". It would not be tough to have a dynamic response check before downloading a file.

"remember host" would be nice also, where I can find a connection I like, and have Limewire remember that connection for future downloads. Kind of like a friendly hosts list. Maybe there are securoty issues here.

Hope this isn't too much! ;-)

I will watch this thread for a week or so, and can supply more info if necessary.