Loading Profile...
Out of heap space when many pending tasks
I added 5gb worth of small photos to the client. The number of pending tasks number grew over a few thousand. Wuala died. When I tried to restart it, it died again. I restarted my computer, and it died when windows started up. I adjusted the registry entry for startup to include -Xmx512M.
The client seems to be working after that. My files are uploading.
The client seems to be working after that. My files are uploading.
I’m unconcerned
4
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.
The best solution from the company
-
Please use the special Wuala1GB.exe for window to increase the java-heap space on windows machines. You can find it here: http://www.wuala.com/Wuala+Community/...
On Linux Systems you can increase the setting in the wuala batchfile. Please set the -Xmx256m option to -Xmx512m a higher number to increase the heap-space.
The company says
this solves the problem
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hm, you mean %appdata%\Wuala\Wuala.exe -silent -Xmx512M works?
What entry did you modify, I didn't find anything really related to settings within Wuala... -
Inappropriate?Ok, I tried to add -XX:+AgressiveHeap to my desktop-link and Wuala started...
Then I added (or I'm currently adding...) ~20 000 files (7 GB) to kill Wuala - no chance! RAM of the VM goes up to 356032k according to the task manager and ~ 186 MB according to Wuala --> About... Box.
No crashes, quite CPU heavy (well, my harddisks are encrypted, so this is expected behaviour) but everything seems fine atm.
I’m excited
1 Comment Add a comment
This solves the problem
-
Haven't tried without the switch though... I'm gonna try that now. -
Inappropriate?Please use the special Wuala1GB.exe for window to increase the java-heap space on windows machines. You can find it here: http://www.wuala.com/Wuala+Community/...
On Linux Systems you can increase the setting in the wuala batchfile. Please set the -Xmx256m option to -Xmx512m a higher number to increase the heap-space.
The company says
this solves the problem
1 Comment Add a comment
This solves the problem
-
Also with the standard 256MB windows client I could add a ~30 MB folder with ~9000 files (resulting in ~16000 pending transactions) without any problems, just fyi.
-
Inappropriate?The 1GB version does not start on my computer.
I just hear the sound of an error but I don't even see an error message or anything else
2 Comments Add a comment
This solves the problem
-
Where did you copy it to? It has to be in the same folder as you standard Wuala.exe...
-
that's what I did...
-
Inappropriate?Error: Could not create the Java Virtual Machine
-
Inappropriate?Hm, I just killed the 1GBWuala.exe... out of heap space.
I'd love to have the .vmoptions file that is mentioned in the FAQ back!
I’m sad
-
Inappropriate?With todays update it should be possible to insert thousands of files at once.
I’m happy about this update
-
Inappropriate?Still having this problem when transferring single files sized in the range of multiple gigabytes (like 9 or 10 gb).
I’m frustrated
-
Inappropriate?With wuala1gb.exe it's still this error when starting. Any solutions or ideas?
Java(TM) SE Runtime Environment (build 1.6.0_13-b03)
.
-
Inappropriate?FOUND A SOLUTION!!
This Java error is connected to Kaspersky Internet Security / Antivirus
You need to uninstall the modules "Spam" and "Privacy"
I’m happy
1 Comment Add a comment
This solves the problem
-
I suppose you only need such software in Windows while the problem also affects other platforms.
-
Inappropriate?Is there currently any solution for this in Windows? I am backing up my photos (~30,000 files) and I can't get Wuala to run for more than like 10 minutes. I have tried the Wuala1GB.exe but it crashes just the same.8 Comments Add a comment
This solves the problem
-
Hi Johnny,
please send in the report wuala produces to find out whats going wrong. Usually, this should not happen anymore or at least very seldom... -
I have clicked send when it prompts me after it crashes. Is this the report that you are referring to, or is there some other way to provide more information.
-
thanks. This is perfect. ;) Oh by the way, did wuala crash several times or was it a one time happening?
-
It crashes continuously. I can't get it to run for more than a few minutes. When crashes it gives the java heap error, and it seems to be related to the output buffer. This problem started as soon as I added my photos folder as a backup folder.
-
In theory, the backup process shouldn't create more than 100 transactions at a time. So I'm not sure why this happened. You should be able to get rid of the error by clearing the transaction cache. Thereby, you will lose all pending changes, but you might be able to work again. If you want to help us to track the cause of the error down, please try starting Wuala with the following modified launcher:
http://www.wuala.com/Wuala%20Communit...
It should create a big file with the ending .hprof the next time Wuala runs out of memory. If you send that to us, we can analyze it.
btw: I couldn't find your sent in reports, is your username johnny? You can also paste the message here. -
I will load it up with the debugging launcher you provided. Where do I send the .hprof file to? My user name is not Johnny. It is jruss. I have told it to send the report on multiple occasions.
-
I have an .hprof file but I am not sure how to get it to you. Here is the output message when it crashes:
com.wuala.common.exception.ApplicationRuntimeException: Java heap space
at com.wuala.obfuscated.TZ.uncaughtException(Z:96)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.ThreadGroup.uncaughtException(Unknown Source)
at java.lang.Thread.dispatchUncaughtException(Unknown Source)
Caused by: java.lang.OutOfMemoryError: Java heap space
at java.io.BufferedOutputStream.<init>(Unknown Source)
at com.wuala.obfuscated.xV.<init>(Z:48)
at com.wuala.obfuscated.qW.a(Z:66)
at com.wuala.obfuscated.ahH.a(Z:40)
at com.wuala.obfuscated.qW.a(Z:53)
at com.wuala.obfuscated.qW.f(Z:1)
at com.wuala.obfuscated.NG.run(Z:120)
at java.lang.Thread.run(Unknown Source)
--------------------------------------------
java.lang.OutOfMemoryError: Java heap space
at java.io.BufferedOutputStream.<init>(Unknown Source)
at com.wuala.obfuscated.xV.<init>(Z:48)
at com.wuala.obfuscated.qW.a(Z:66)
at com.wuala.obfuscated.ahH.a(Z:40)
at com.wuala.obfuscated.qW.a(Z:53)
at com.wuala.obfuscated.qW.f(Z:1)
at com.wuala.obfuscated.NG.run(Z:120)
at java.lang.Thread.run(Unknown Source)
</init></init></init></init> -
Hm.. the simplest way to get the .hprof file would be to upload it to wuala and send me a link to it. Does Wuala also crash if you use a dummy account? (Btw: my email: luzius@wuala.com)
-
Inappropriate?I put a description with the error message and two .hprof files in this folder in the /Wuala Community/Bugs/Incoming folder:
http://www.wuala.com/Wuala%20Communit...
It was quite the ordeal to stop the backup folder from uploading, so that I could get these debug files uploaded. I ended up having to delete my whole backup folder, and then delete it from the trash before I could get it to stop uploading. I looked into it and it seems that is a separate issue though.4 Comments Add a comment
This solves the problem
-
Thanks, I'm downloading them now and will analyze the dumps. I'd recommend to delete the dumps again from the community page as they contain a complete dump of everything Wuala had in memory at that time, so someone who is technically savvy might find out things about your files (names, content, etc.) if they were in memory at that time of the dump.
-
I think I've found the memory leak. It will be fixed in tomorrows update. Thanks for your help.
-
Thanks for the security tip. I cleared those files out. I am glad to hear that the leak got tracked down. Will Wuala update automatically? If so how will I know that I am updated to the fixed build? I want to make sure it is fixed before I attempt to back up that folder again.
-
My client updated to the Wuala Beta PC 236 build today. I have uploaded several GB over a period of several hours without incidence. I just wanted to confirm that the memory leak appears to be fixed on my end. Thanks for the quick response. I am thoroughly impressed.
EMPLOYEE
EMPLOYEE
EMPLOYEE
