|
LW using too much CPU? PROBLEM SOLVED! Windows suffers from a similar problem with Java, which was where I got the idea to try this. A Jar file is just a compressed set of Java classes. You can invoke them in the terminal via java -jar, just like if it were a class. The LimeWire "app" that you see *kind of* does the same thing. Anyways: 1. Open Terminal 2. Type "java -jar " and drag in the file "LimeWire.jar" in the LimeWire folder. i.e. "java -jar /Applications/Limewire/LimeWire.jar" LimeWire will now start up. DO NOT quit Terminal, and try to live with the fact that instead of the LimeWire icon in the dock, you get Apple's generic Java Application icon. What was using 70-80% on my dual 1Ghz is now using between 5 and 20. Have fun! Mike:D |
Woops, look's like there's nothing wrong with quitting Terminal while LimeWire runs. |
Chip, To repeat my reply to Dan on his port, your fix seems to be working on my G4/400MHz. This is clearly a programming bug -- how do we submit a bug report? |
Beats me jannuss. In the meantime, I'd just use my method, since it's not to obtrusive when you hide the Terminal. Also, I was wrong about quitting Terminal. Ending the Java process may quit Limewire. |
This is extremely odd behavior. It's possible that something in running it from the command line prevents you from becoming an Ultrapeer (you can see your Ultrapeer status in the connections tab in the lower left -- if it says "Ultrapeer," then you're an Ultrapeer, otherwise you're a "leaf"). Otherwise, there should be no difference between running LimeWire from the command line and running it from the alias. |
It's also extremely odd behavior that LimeWire does what I found the fix for in the first place! Launching the LimeWire app should just be a GUI front end that tells the system: java -jar /Applications/LimeWire/LimeWire.jar Which it musn't be, because then there shouldn't be any problems with using either method. The app itself is definitely not just an alias to the Java call. It's much too big a file for that. If LimeWire has problems with this, then LimeWire is being programmed extremely poorly. There are a number of other reasons for this being true, besides this. Read around the forums and you'll see. People shouldn't be writing Java apps if they don't understand the basic idea of what Java is for. |
Actually the proper command for running LimeWire should be java -jar /Applications/LimeWire/RunLime.jar The problem is not caused by LimeWire's java code, but either by the run script or MacOSX' WindowManager, that does not properly handle the command to start the java app. Since the WindowManager is the task that uses 70%-80% of the cpu resources I assume this is a MacOSX bug. |
Ahh...yeah. Yes, LimeWire wraps the call to java -jar RunLime.jar in the standard Apple app builder. Thanks. |
trap_jaw is correct that the underying command is to: java -jar /Applications/LimeWire/RunLime.jar We'll investigate the Window Manager issue more thoroughly. On our 10.1.2 system, we saw no difference between the command line execution and the normal execution, but I'll check on Jaguar and have a look at all processes involved. Thanks! |
CptChipJew- Just to clarify, the call to java -jar RunLime.jar does not simply launch the ui -- it launches the entire java application, including all connection threads, TCP and UDP listening threads, etc. OS X has it's own custom method of launching java applications (launching java applications is basically os-specific because there are multiple ways of executing processes via aliases, shortcuts, exes, etc, on different operating systems). In LimeWire on OS X, we use the executable automatically generated by InstallAnywhere. On Windows, I wrote a custom executable to locate the latest java executable and run it. Thanks. |
Funny you should mention that. When attempting to run LimeWire on a Win2k machine I have, the javaw process starts, using 100% of the CPU, and LimeWire doesn't launch. Of course, java -jar makes it all work fine. |
Do you have the JRE installed, the JDK installed, or both on your w2k machine? Which installer did you use? |
Both, 1.4.1_01 FCS, which seems to work with everything I do involving Java. |
Which installer did you use to install LimeWire? If you run the executable directly, nothing happens? Did you customize your registry in any way? Thanks. |
I used the Windows installer.....what else? |
There are two windows installer -- one for that allows you to specify language, one that doesn't. There's also a zip file with the raw files, and you also could have checked it out directly from CVS. |
Guys, I've started a new thread on a related problem: it seems that the java bug/incompatibility doesn't allow for moving shared files to a partition other than the system! I guesst if I want to get involved in this I'm going to have to learn Java -- can any one recommend a good book? |
The only book I ever read on Java was Oreilly's "Java in a Nutshell" - it's sufficient - if you don't want to do it professionally. |
Quote:
Hope this helps.... |
I would give the "Core" books from Sun a shot -- both volume 1 and volume 2. Those will teach you the language, as will "The Java Language Specification" and "The Java Programming Language." Then, to write good java, I would highly recommend "Effective Java." |
Apologies for the non sequitur, but it would be really good of one you developers to take a look at the posts on "Could not move to library". This is not in regard to low disk space, but a new, extremely troublesome problem introduced with the latest edition of Limewire. Until two days ago, I had few problems with limewire, and was considering paying the reasonable fee. I downloaded the new version (after dismissing the nag dialogue 5000 times), and now am stuck with inoperable software. This is not cool, and a few comments from you in some of these posts might point people in the right direction. |
We'll have a look at it. Thanks. Does it happen for you with every download? |
I have tried this numerous times, and it always returns an error, as follows: STARTUP ERROR LimeWire version 2.7.13 or above Java version 1.3.1 from Apple Computer, Inc. Mac OS X v. 10.2.2 on ppc Free/total memory: 1692560/2031616 java.lang.ClassNotFoundException: com.limegroup.gnutella.gui.Main at java.net.URLClassLoader$1.run(URLClassLoader.java: 195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.j ava:183) at java.lang.ClassLoader.loadClass(ClassLoader.java:2 94) at java.lang.ClassLoader.loadClass(ClassLoader.java:2 50) at RunLime.main(Unknown Source) FILES IN CURRENT DIRECTORY: /Users/lewinb/.CFUserTextEncoding LAST MODIFIED: 1031648962000 SIZE: 3 /Users/lewinb/.DS_Store LAST MODIFIED: 1039562719000 SIZE: 12292 /Users/lewinb/.lpoptions LAST MODIFIED: 1039153228000 SIZE: 24 /Users/lewinb/.phoenix LAST MODIFIED: 1036777983000 SIZE: 136 /Users/lewinb/.Trash LAST MODIFIED: 1039562719000 SIZE: 102 /Users/lewinb/3838-3H839 Economiser.pdf LAST MODIFIED: 1038617802000 SIZE: 61964 /Users/lewinb/Applications LAST MODIFIED: 1037729113000 SIZE: 204 /Users/lewinb/Bayerisch Rundfunk LAST MODIFIED: 1032410974000 SIZE: 714 /Users/lewinb/Desktop LAST MODIFIED: 1039562719000 SIZE: 748 /Users/lewinb/Desktops LAST MODIFIED: 1039413981000 SIZE: 3026 /Users/lewinb/Documents LAST MODIFIED: 1039424774000 SIZE: 1122 /Users/lewinb/Drive 10 v.1.1.1 Serial LAST MODIFIED: 1034147910000 SIZE: 15 /Users/lewinb/Dues Form.pdf LAST MODIFIED: 1033619687000 SIZE: 190448 /Users/lewinb/EtherPeek SN LAST MODIFIED: 1035101323000 SIZE: 17 /Users/lewinb/Face-Shirt edited.jpg LAST MODIFIED: 1037185480000 SIZE: 58717 /Users/lewinb/Face-Shirt.jpg LAST MODIFIED: 1037183679000 SIZE: 31384 /Users/lewinb/G-Force 2.1 Installer LAST MODIFIED: 1034325924000 SIZE: 345969 /Users/lewinb/Incomplete LAST MODIFIED: 1039556965000 SIZE: 25500 /Users/lewinb/Jf504demoHandango Folder LAST MODIFIED: 1038696995000 SIZE: 306 /Users/lewinb/LexiDrugs2000 Install LAST MODIFIED: 1038189240000 SIZE: 136 /Users/lewinb/Library LAST MODIFIED: 1039553425000 SIZE: 1122 /Users/lewinb/Movies LAST MODIFIED: 1030948108000 SIZE: 102 /Users/lewinb/Music LAST MODIFIED: 1038123093000 SIZE: 816 /Users/lewinb/Not Shared LAST MODIFIED: 1039557017000 SIZE: 1326 /Users/lewinb/Pictures LAST MODIFIED: 1033370747000 SIZE: 170 /Users/lewinb/Political pictures LAST MODIFIED: 1035094165000 SIZE: 1088 /Users/lewinb/Public LAST MODIFIED: 1034012541000 SIZE: 170 /Users/lewinb/Shared LAST MODIFIED: 1039557561000 SIZE: 1394 /Users/lewinb/Sites LAST MODIFIED: 1035445854000 SIZE: 204 /Users/lewinb/Year Round School Research LAST MODIFIED: 1034823584000 SIZE: 374 _____ Do you need to be logged in as root or something to get this to work? It appears to be searching only my home folder, rather than the applications folder, where Limewire actually resides. |
That's very strange. What version was giving you the problems you mentioned previously? Have you tried 2.8.0? |
Where the heck do you get 2.8? I just downloaded this from the Limewire site two days ago. Isn't this the most current edition?!:confused: I'm not sure I follow you. I'll be glad to try 2.8, if you can tell me where to get it. |
Addendum: I just went back and tried the first post... type "java -jar " then drag limewire.jar to it, [return] That worked perfectly, whereas RunLime.jar didn't. Got any ideas? Should it work this way? After working for a few minutes, I went to "about Limewire" to see what version this claims to be. It never came up, and after a few moments, Limewire quit. Terminal returned this: lewinb% java -jar /Applications/LimeWire/LimeWire.jar kCGErrorFailure : CGTranslateCTM is obsolete; use CGContextTranslateCTM instead. CGGStack.c:87: failed assertion `stack->count > 0' Abort SO, I tried it a second time, and found that as soon as I clicked anywhere on the menubar (in this case to get stats), Terminal returned: lewinb% java -jar /Applications/LimeWire/LimeWire.jar kCGErrorFailure : CGTranslateCTM is obsolete; use CGContextTranslateCTM instead. BUT, Limewire has not as yet quit. |
OK, now, after letting it sit here for about an hour, it's pretty much at a standstill. The spinning beachball of death is continuous, and Termal has now returned the following: java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> java.lang.OutOfMemoryError <<no stack trace available>> |
Very interesting -- thanks for all of the debugging information. I assume you got all of these errors with LimeWire 2.8.0 beta? The problem appears to be related to us using an outmoded API for the About and preferences window. Apple has changed the API for this a couple of times now, so we might not be doing everything we should. I'm also starting to become convinced that there are serious problems with LimeWire on 10.2.2 (I'm using 10.2.1 here). Did you ever use LimeWire before you had 10.2.2, and did you experience these types of problems? Thanks again. |
2.8.0 is unusable on Mac OS X Adam. I'm still on 10.2.1 running LimeWire 2.8.0 Beta 1. impossible to launch LimeWire from the application. Window Manager claims 97% of the CPU and Forced Quit takes 5 minutes to complete. 2. launching from the Termianl Window allows LimeWire to run normally, but it may or maynot be possible to run other applications simultaneously. I haven't yet found a pattern for when Window Manager goes bonkers and when it doesn't. 3. Even if eveything runs OK, all (count them ALL) downloads end with the Unable to move to Library bug. In short, 2.8.0 is unusable on Mac OS X. |
Are you running a system with multiple users? Did you get these problems with 2.7.13? Thanks. |
Powerbook G4 500Mhz 512Mb RAM OS 10.2.2 Limewire 2.8.0 Limewire: peaks at 90% CPU on startup 10%-20% CPU when running idle with stable connections peaks of 40%-70% CPU when searching More or less constant at 10% memory (50Mb) Window Manager peaks appear to be unrelated to Limewire. Mine operates at 2%-7% CPU normally - with or without Limewire running. Running the mouse pointer along the Dock with magnification on, for example, will cause the WM to peak at 60% CPU for a second or so. Many other normal operations (like window or application swapping) will cause similar peaks. I tried starting Limewire from the Terminal and got similar CPU percentages ('com.limegroup.gnutel' instead of 'Limewire' in the Process Viewer). I have successfully downloaded and uploaded files with no specific problems apart from the 'Could Not Move To Library' error which occured twice with one specific file (illegal characters?). |
Single user, very standard system. I moved to OS 10.2.1 about a month ago when my ADSL line was installed. My kids immediately downloaded LimeWire (2.7.3) and started sharing files. They've kept the computer so busy that I havedn't had a chance to install much more: Netscape 7, AppleWorks, a few games and utilities. I moved to 2.7.13 because of the Window Manager bug. Once everything looked OK, I decided to organize all may large .avi and .mpg files into a single folder (2GB) on a separate partition from the systems disk. When I did that everything fell apart. At the suggestion of some one on this forum, I downloaded 2.8.0Beta in the hopes that it would solve my problems -- it did, and created a rash of new ones. I repeat what I said earlier, 2.8.0Beta doesn't appear to me to be anywhere near release. Note: in my problem #2 above, I said that I didn't know when 2.8.0 would allow other applications to run and when not. I think LimeWire is OK if it's the very first application launched after startup. BUT, I suspect that if you launch other applications, exit, and launch again too many times, eventually Window Manager will go crazy. |
Reply to Mac Terminator above: Sure, I've seen Window Manager peak to 60% and more on many occasions with different applications. The problem that others and I are experiencing is this: with LimeWire running, you launch some other application [even something simple like System Preferences], and Window Manager jumps to 60-90% and stays there. Sometimes it will settle down after 5, 10, or even 15 minutes and sometimes it won't. Totally inconsistant which makes the problem even harder to identify. Just out of couriosity: how large is your Shared folder and is it physically on your Systems disk? |
I think this is very likely related to the use of the external drive, as other users have mentioned similar problems. Can you try changing the shared and save directories to be on the same drive as LimeWire? I also suspect that this is precisely the cause of the "Could Not Move to Library' bug. |
MacTerminator- I've seen almost precisely the same behavior on my system -- thanks very much. It's good to know I'm not going insane (at least not as far as LimeWire goes =). |
Quote:
Quote:
But I've just done a test setting my LW Saving folder on an External 80Gb Firewire drive and downloading a couple of small files with no errors. This has always been a big mystery to me. I have three Macs (a dual 1 GHz Quicksilver, A Powerbook G4 500Mhz and a Powerbook G3 233Mhz). I've done tests several times between them: doing a clean installation of the system (usually OS9 as the PBG3 doesn't really have enough muscle for OSX) and installing the same software on two or all three computers. And I've found that even on computers with exactly the same configuration (though obviously not the same model) the same program can work perfectly on one and be practically unuseable with errors on another. Gremlins? You tell me.... |
Quote:
|
Reply to Adam Fisk above: My Shared Folder is on the same physical [internal] disk, but on a different partition from the System. I can't move Shared back to the System parition because there isn't enough room -- the reason I moved it out in the first place. I've always been of the opinion that separating user data from systems and applications was a healthy thing. I probably won't have time til late tonight or even tomorrow, but I'll do an eperiment with a small Shared Folder on the systems partition. Back to you then. Janet |
Peculiar 1 Attachment(s) Since installing the beta, some of the aforementioned problems are taken care of (for me). However, I have noticed that every time I leave it alone for an extended time (ie when I am asleep) it quits. I have my PB's monitor set to go off a after a few minutes of inactivity. I can tell by the file modification times that Limewire always quits just a few minutes after I leave it. Could the monitor going off somehow affect Limwire? Anyone else notice this? Bruce PS when I installed the beta, the installer still left the attached file on my desktop, as it did with 2.7. |
Experiments with LimeWire -- no joy for Adam Fisk: I performed the following experiements this morning: Running LimeWire 2.8.0Beta with Max OS 10.2.1 on a G4/400MHz with 512MB memory: 1. Create a Shared Folder on the Systems disk with two .avi files (160MB total); empty Incomplete Folder: restart computer 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 97%, the colored beach ball spins and spins, the computer is totally frozen. After seven minutes I shut off the power. 2. Repeat the test launching LimeWire from the Terminal Window --> identical results. 3. & 4. Empty the Shared Folder and delete the Incomplete Folder and repeat tests 1 & 2 --> identical results. Note: I have an external CD-RW on the FireWire port and a scanner on my SCSI port [I have to switch to System 9 to use it]. The lab tech at my supplier's says that these sometimes cause problems with OS X -- I've yet to experience any. Janet |
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? |
Oops -- Make that 10.2.2 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 |
More tests -- Less joy 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 |
Ever so slightly good news 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 |
| All times are GMT -7. The time now is 11:45 AM. |
Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2025, vBulletin Solutions, Inc.
SEO by vBSEO 3.6.0 ©2011, Crawlability, Inc.
Copyright © 2020 Gnutella Forums.
All Rights Reserved.