Thanks so much for taking the time to test that configuration. We have spoken with a number of people who have had similar problems related to firewire drives. Can you try disconnecting your firewire CD-RW altogether an running again?

Adam,

I'll do the FireWire tests todnight, if I can, but first an apology.

I'd planned to hold off upgrading to 10.2.2 until I'd finished all these tests -- no need to add yet another parameter to the equation -- then my daughter mentions off-handedly that she'd upgraded by system to 10.2.2 yesterday!

So, all my posts up to Thursday morning apply to 10.2.1; from Thursday afternoon it's 10.2.2.

Ah, the joys of children.

Janet

for Adam Fisk:

I performed the following experiements this morning:

Running LimeWire 2.8.0Beta with Max OS 10.2.2 on a G4/400MHz with 512MB memory:

1. Unplupped my CD-RW [FireWire] and restarted the computer . . .
Create an empty Shared Folder on the Systems disk; deleted the Incomplete Folder:
launch PPTP
launch Process View
launch LimeWire (from the application)
--> runs fine. enable incoming searches, do a few searches of my own, start a download. All's well.
launch another applications [AppleWorks]
--> Window Manager climbs to 80+%, the colored beach ball spins and spins, the computer is totally frozen. After five minutes I shut off the power. [Note: Process Viewer does not function correctly under these cercomstances, so the cpu % numbers are only estimates.]

2. Repeat the test launching LimeWire from the Terminal Window
--> identical results.

3. & 4. Unplugged the scanner [SCSI] and restart the computer . . .
Empty the Shared Folder; delete the Incomplete Folder; repeat tests 1 & 2
--> identical results.

5. & 6. Many users have Classic start up automatically (I don't), so with the CD-RW and scanner still unplugged, I started Classic . . .
Empty the Shared Folder; delete the Incomplete Folder; repeat tests 1 & 2
--> identical results.

7. & 8. As a final check, I went back to LimeWire 2.7.13 and with the CD-RW and scanner still unplugged . . .
Empty the Shared Folder; delete the Incomplete Folder; repeat tests 1 & 2
--> identical results.

Conclusion: under 10.2.2 LimeWire functions as a stand-alone system only!!!

Now, the final test will be to put my system back together, restore my large Shared and Incomplete folders (on a separate partition from the System), and run stand alone. I fear all downloads will hit the "Unable to Move to Library" bug I started out with and that will be the end of LimeWire on my computer until further notice.

Stay tuned.

Janet

Janet

LimeWire did function OK as a stand-alone system. Downloads completed and went safely to the shared library. And several of my files were uploaded.

Of course I had to try over 40 (forty!) download requests until I found two that would actually download. All the others stayed in Requery loops for over 12 hours. [No one has yet explained to me how it is that I find a file with a search, mark it for download, and poof! the owner's host is unavailable -- busy responses I understand, but not this.]

Note: twice during the night (I don't know when, I was asleep), a bug report window opened asking me to save debug info and mail it to LimeWire. I tried to press "choose" to select a filename, but "OK" was the only choice that responded. This morning there were no debug files anywhere on the disk.

Janet

Thanks very much for taking the time to so thoroughly test these various configurations. There clearly seems to be a Window Manager issue that appears to be unrelated to any FireWire problems. I'm really unsure how to attack the problem right now, as we've still been unable to reproduce the jump in Window Manager resources. I'll keep trying, though, and I'll continue to ask around.

Unfortunately, this means that we won't have a fix soon. There may be a conflict between LimeWire and another specific application, and there may also be a bug in the Apple version of Java that we're unaware of. It would be interesting to see if other Java-based applications suffer from the same Window Manager issue. Unfortunately I can't think of any that would be a simple download/install right now.

Thanks again. We're releasing 2.8.1 shortly, but without any fixes for this particular problem.

This is fascinating. I tried the Terminal trick too. No difference in CPU use or performance with X 10.1.5. The Terminal window shows a long list of what seem to be error messages regarding Cookies, GUIMediator, MacEventHandler, FileOutputStream, etc.

I'm having kernel panics like Janet with LW 2.8.5 which I'll bring up in a new thread. It seems unrelated to running other programs however.

Tom