Loading Profile...
javaw.exe erzeugt hohe CPU- und RAM-Auslastung
Beim Betrieb von wuala sorgt "javaw.exe" (Java 2 RE 1.6.0_07) immer wieder Minuten lang für bis zu 100% CPU-Auslastung. Die Speicher-Auslastung liegt dauerhaft bei 240 MB. Woher kommt dieser Ressourcenhunger? So ist auf Dauer jedenfalls kein sinnvolles Arbeiten am PC möglich!
Ist das ein bekanntes Problem, oder geht es nur mir so? (Ich verwende Win XP SP2, weitere Details zu meinem Rechner findet ihr hier: http://www.sysprofile.de/id39788 )
Danke für eure Hilfe!
---english---
While I'm running wuala, the CPU utilization of "javaw.exe" (Java 2 RE 1.6.0_07) consistently goes up to 100% for several minutes. Memory utilization is always around 240 MB. Where does wuala's resource hogging come from? It's pointless to run this piece of sw on my PC, when constant working gets nearly impossible!
Is this a known problem, or does this only happen to Me? (I'm running Win XP SP2, further details about my PC can be found here: http://www.sysprofile.de/id39788 )
Thanks in advance for your help!
Ist das ein bekanntes Problem, oder geht es nur mir so? (Ich verwende Win XP SP2, weitere Details zu meinem Rechner findet ihr hier: http://www.sysprofile.de/id39788 )
Danke für eure Hilfe!
---english---
While I'm running wuala, the CPU utilization of "javaw.exe" (Java 2 RE 1.6.0_07) consistently goes up to 100% for several minutes. Memory utilization is always around 240 MB. Where does wuala's resource hogging come from? It's pointless to run this piece of sw on my PC, when constant working gets nearly impossible!
Is this a known problem, or does this only happen to Me? (I'm running Win XP SP2, further details about my PC can be found here: http://www.sysprofile.de/id39788 )
Thanks in advance for your help!
I’m frustrated
6
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
Create a customer community for your own organization
Plans starting at $19/month
-
-
Inappropriate?...or it's time for people to actually LOOK at the threads getsatisfaction suggests! D'oh!
-
Inappropriate?anyhow, the thread you suggest is just about memory...while I do not really care about memory as my machines have enough, its the high CPU load that is really bad.
I’m frustrated
-
Inappropriate?Agreed -- it's the maxing out the CPU thats killing me!!!
I'm running XP with 1.5GB RAM, so I could care less about the mem usage.
I have also found that this (the CPU 100%) only seems to happen, when it is currently uploading data. When it is just running doing it's thing with the space I am trading, it does not run the CPU up. Only when I add stuff to my files. (and it doesn't just max out, when it's doing that initial "add files..." part, that has the progress bar -- even after that is done, and it's just uploading the data, (little green bars by the files in wuala) it still max's out the CPU)
Another small detail I noticed -- that may or may not be significant. I started wuala, uploading when I was done with my PC one night. I normally stay logged into the PC, but I remote desktop'ed to it real quick that night -- so it was at the welcome screen in the morning. I logged in, and noticed first thing that wuala was maxing my CPU -- So I immediately un-minimized task manager --- and looked at my CPU graph -- I could see all the way back, it was running at >10% -- and it just spiked to a 100% plateau when I logged in. I haven't tested this to see if I could recreate it -- but it seemed weird, that it would max it out only after I logged back in.
This only happens on 1 of my PC's. On my others, when it is doing the initial "add files...." part -- it doesn't max out the CPU, but it does tax it to about 30% --- and once the "add files..." part is over, and it is just uploading data to to the network, (green bars by files), the CPU goes back down to <10> part is over, and its just uploading.
If you want me to troubleshoot/try anything, or provide logs, an everest report, a hijackthis report, or anything else that might help, just let me know.
I’m frustrated
2 Comments
Add a comment
This solves the problem
-
EDIT: I just checked again -- and this problem seems to be fixed (or perhaps it doesn't happen all the time) --- I'll assume it's fixed, and I will post back, if I experience the problem again. -
EDIT: While it doesn't seem to max out during upload anymore. It is now maxing out, when it is "Maintaining" a file.
-
Inappropriate?Oi! Here as well! Maintaining files seems to use quite some CPU cycles (wasn't always like that...). I just logged in on my storage node and clearly see the reported behaviour. Wuala also reports (inside Wuala - about box!) 116 MB(!) RAM used.
Something seems really wrong here...
Client: 108
Windows 2008 64bit, FSI activated + works flawlessly
After some time however the usage went down. Maybe Wuala did calculate new fragments?!
I’m unsure
-
Inappropriate?I keep getting this program randomly, when uploading/downloading/maintaining. Restarting wuala, seems to fix the problem -- but its really annoying.
I’m annoyed
-
Inappropriate?It's really bad. When I restart wuala it's better in the first time but the RAM usage is running up to 290 MB and then also the usage of the CPU
1 Comment Add a comment
This solves the problem
-
RAM is not an issue since its a pure cosmetical problem. CPU seems to be high when maintaining files sometimes, so I guess Wuala recalculates fragments or something...
EMPLOYEE
