Wuala crashes on my Windows Vista 64 bit!

I've updated Wuala, disabled 'filesystem integration' in the options, and.... it runs!
Thanks Luzius!!! (Luzius the user ;)

Have had the same probleme here but Luzius' hint did a good job :-)

Yep same problem, its running ok now but when will filesystem integration work ok in Vista 64bit?

I t used to only crash when wuala closed or when a network interface got disconnected. Now it seems like it will sometimes crash at random.

Quote from download.wua.la:

"Runs on Win 2000, XP, Vista 32-bit (64-bit not yet supported)."

It runs OK, for various definitions of OK, on windows Vista x64 using a 32bit VM.

Runs pretty stable for not being supported, Marcos. Only FSI isn't working (yet) but I can live with that.

BTW, 64-bit shouldn't be that hard to implement because most of java-stuff is available for 64-bit systems.

Same problem:

This comes randomly in 0-2 minutes after start up.
It works OK in my other 32-bit Vista computers. I updated Java runtime to brand new but does not help.
I have to try the trick to disable filesystem integration...

Win32NetBios on 64bit?

Wuala ONLY uses 32bit java on windows. But it links into a 64bit DLL i think.

I got the same thing on Windows XP 64-bit.

I have also Windows XP 64bit and I even can't create a new account because it crashes instantly...

Try Adding "nojlan" to Wuala.cfg (on a new line)

Vista:
%appdata%\..\Local\Wuala\Wuala.cfg

I only get crashes on Vista x64 when I suspend (I'm guessing due to the network interface being disconnected). I guess I should be counting myself lucky

Anything that causes a nic to become disconnected will piss off FSI on x64. Sad but true. But of all the things to go wrong, yes I too consider myself lucky as well.

Deathbob - I don't have Wuala.cfg file anywhere on my computer (I searched everything including hidden files). I think Wuala freezes before it creates cfg file. I hope that someone will solve this problem because I need to backup some of my files and I can spare more than 100GB of my free HDD space to Wuala community. I just need it working on XP 64bit :(

(Yells for Wuala Employee)
Is it possible to create a Wuala.cfg and have wuala use it or is there some other prerequisite before it would look for it?

I've installed Wuala on 32 bit Windows XP and copied the %appdata%/Wuala folder to my Windows x64 with changes in wuala.cfg Still no success - it is crashing everytime when I try to login.

@Roger: I use Comodo Firewall (one of very few working on XP x64) and no antyvirus software at all. But it doesn't matter if I have firewall activated or not. I'm launching Wuala and after about 15 seconds of doing nothing (I even don't press any buttons) it just freezes.
I don't know if it helps but my hardware configuration is:
CPU: Core2Duo E8200
MB: Gigabyte EP35C-DS3R
RAM: 6GB (2x2 + 2x1)
HDD: 2x640GB (Raid0) + 160GB + 250GB
GFX: GeForce 7900GT XFX

Software:
Windows XP 64bit SP2 ENG (with all updates)
Java: JRE Version 6 Update 7 build 1.6.0_07-b06
Security software: Comodo Firewall Pro 3.0.25.378

I also use VMware server with 2 virtual network interfaces (I hope that doesn't cause any trouble? It never did.)
My computer is behind NAT but I can forward any port if I need.

When it crashes its "Windows needs to close java" or whatever right? Not the submit bug Wuala Window? Or does it say nothing?

Wuala window just freezes. There is no error message. I can't even move the Wuala window. I can only press ctrl+alt+del and kill the app.

Sounds like an infinite loop.

I checked if this can be an infinite loop and I think it can't (because it eventually finished with an error message). When Wuala crashed process called dumprep took 50% of CPU power (100% of one core).


After a minute or two an error message appeared:

I'm 99% sure FSI the cause of the javaw exception.
I don't know if FSI is the inital cause of the crash.

It takes 15 Seconds to hang? Can you go to options and disable File System Integration in that time? Assuming you made an account on your 32bit system.

i've got the same issue.
@stuff: you may get an teamviewer session to my pc, to see the problem in action...

can't this also be done via Options->General-> and a not-checked box at "integration.. filesystem..." ?

I've rechecked everything, and Wuala is working now with the "nojlan" option and the whole wuala directory copied from 32 bit windows. I hope it'll work stable now.

P.S.
I would be nice to create a simple installer allowing user to create account and make some settings before launching main wuala app. It could also detect the type of operating system and disable functions that don't work :)

We have not been able to find a reason why on some x64 FSI crashes and others it works fine.

My Wuale crahses and I have been disabled the file integration.

This is my start log with versions info:

Wuala Applet v10 Log on VISTA64
Send problem reports to: bug_high_prio@wua.la
1ms Log time reset
208ms Connecting to update3.wua.la:443 possible
215ms Found existing configuration: C:\Users\Feliciano\AppData\Local\Wuala\Wuala.cfg
217ms Configuration loaded C:\Users\Feliciano\AppData\Local\Wuala\Wuala.cfg
345ms No running instance found: null
346ms No startup script defined in config.
349ms Creating startup script in C:\Users\FELICI~1\AppData\Local\Temp\loader2.jar
367ms Starting Wuala, using C:\PROGRA~2\Java\JRE16~1.0_0\bin\javaw.exe
368ms Full command: C:\PROGRA~2\Java\JRE16~1.0_0\bin\javaw.exe -ea -XX:MaxHeapFreeRatio=30 -XX:MinHeapFreeRatio=10 -Xmx256m -Xms50m -cp C:\Users\FELICI~1\AppData\Local\Temp\loader2.jar com.wuala.loader2.Loader2 -page http://wua.la/
3189ms Wuala Commandline
3242ms Once Wuala is running, you can send commands to it by calling
3294ms it again with the desired command as argument (e.g. './wuala logout)'
3346ms The commands will be passed on to the first instance.
3397ms Execute './wuala help' for a list of available commands.
3474ms Click event 226, 51 in java.awt.Rectangle[x=0,y=0,width=248,height=60]
4988ms Wuala Loaded, page=http://wua.la/
4988ms Loading took 4988ms
5044ms Sending report to loader@wua.la

And after some minutes after the applications crashes..

Crashes as in java.exe has been closed error or what?

My PC:
6GB DDR2 RAM
AMD X2 6400+ CPU
1,36 TB HDD
Windows Vista Ultimate x64
Wuala Runs fine after deaktivation of FSI

PS.:
Sorry for my Bad english. im from Germany. :p

darn, now i've got a similar problem. i had wuala runing on a vista 64 build for many months, but now it won't launch. after clicking the .exe it begins to load, than a get a crash report option, send/ don't send. i'll do a backup of the machine.dat and fifty GBs of fragment files, some time this weekend and see if i can re-install the main app.

here's the error log:


com.wuala.common.exception.ApplicationRuntimeException: 0,0
at com.wuala.obfuscated.TZ.i(Z:171)
at com.wuala.obfuscated.yJ.a(Z:287)
at com.wuala.obfuscated.yJ.a(Z:129)
at com.wuala.platform.Wuala.launch(Z:26)
at com.wuala.loader2.Loader2.startInstance(Loader2.java:65)
at com.wuala.loader2.Loader2.start(Loader2.java:47)
at com.wuala.loader2.Loader2.main(Loader2.java:135)
Caused by: java.lang.AssertionError: 0,0
at quickbase.internal.entries.Block.calcBlockSize(Block.java:95)
at quickbase.internal.entries.AddEntryChecksum.getValue(AddEntryChecksum.java:184)
at quickbase.internal.consumer.CompactorConsumer.flush(CompactorConsumer.java:82)
at quickbase.internal.files.DataFile.visit(DataFile.java:105)
at quickbase.internal.files.DataFiles.visitAndClear(DataFiles.java:93)
at quickbase.SingleMapDatabase.internalCompact(SingleMapDatabase.java:388)
at quickbase.SingleMapDatabase.init(SingleMapDatabase.java:122)
at quickbase.SingleMapDatabase.<init>(SingleMapDatabase.java:97)
at quickbase.SingleMapDatabase.<init>(SingleMapDatabase.java:75)
at quickbase.MultiMapDatabase.<init>(MultiMapDatabase.java:34)
at com.wuala.obfuscated.vF.<init>(Z:32)
at com.wuala.obfuscated.Id.<init>(Z:79)
at com.wuala.obfuscated.CR.<init>(Z:45)
at com.wuala.obfuscated.dH.<init>(Z:66)
at com.wuala.obfuscated.dH.a(Z:103)
at com.wuala.obfuscated.dH.a(Z:96)
at com.wuala.obfuscated.yJ.a(Z:319)
at com.wuala.obfuscated.yJ.a(Z:251)
... 5 more

--------------------------------------------

java.lang.AssertionError: 0,0
at quickbase.internal.entries.Block.calcBlockSize(Block.java:95)
at quickbase.internal.entries.AddEntryChecksum.getValue(AddEntryChecksum.java:184)
at quickbase.internal.consumer.CompactorConsumer.flush(CompactorConsumer.java:82)
at quickbase.internal.files.DataFile.visit(DataFile.java:105)
at quickbase.internal.files.DataFiles.visitAndClear(DataFiles.java:93)
at quickbase.SingleMapDatabase.internalCompact(SingleMapDatabase.java:388)
at quickbase.SingleMapDatabase.init(SingleMapDatabase.java:122)
at quickbase.SingleMapDatabase.<init>(SingleMapDatabase.java:97)
at quickbase.SingleMapDatabase.<init>(SingleMapDatabase.java:75)
at quickbase.MultiMapDatabase.<init>(MultiMapDatabase.java:34)
at com.wuala.obfuscated.vF.<init>(Z:32)
at com.wuala.obfuscated.Id.<init>(Z:79)
at com.wuala.obfuscated.CR.<init>(Z:45)
at com.wuala.obfuscated.dH.<init>(Z:66)
at com.wuala.obfuscated.dH.a(Z:103)
at com.wuala.obfuscated.dH.a(Z:96)
at com.wuala.obfuscated.yJ.a(Z:319)
at com.wuala.obfuscated.yJ.a(Z:251)
at com.wuala.obfuscated.yJ.a(Z:129)
at com.wuala.platform.Wuala.launch(Z:26)
at com.wuala.loader2.Loader2.startInstance(Loader2.java:65)
at com.wuala.loader2.Loader2.start(Loader2.java:47)
at com.wuala.loader2.Loader2.main(Loader2.java:135)</init></init></init></init></init></init></init></init></init></init></init></init></init></init>

Hi tigurr,

have you had success with the re-installation?

Thanks guys! i have yet to try this solution on the original PC that was crashing, but i was having problems with a vista 32-bit, on a different PC, the file integration would fail, but the wuala client would load, and i would get online fine. Luzius' solution solved it. to a degree, i am still getting

connection type B limited readability error

but at least one of my machines is kind of back online.

here is the error log:

Analyzing Connection...
Got answer from Ping Server 'A', your external address is '/70.71.181.226:7969'.
Got answer from Ping Server 'B', your external address is '/70.71.181.226:7969'.
Trying to find UPnP router...
Found UPnP router: http://192.168.0.1/root.sxml
Error while communicating with router: Detailed error code :501, Detailed error description :Internal Server Error
'/70.71.181.226:7969' accepts incoming connections from contacted addresses.
Connection type B: Limited reachability

okay, this fixed the problem on the 64-bit vista box. it's back up and running, with a connection type A. Thanks so much, for everybody's help. i'm not to sure as to why my 32-bit vista box currently has the limited reachability problem, but i'm still glad i'm no longer losing on-time.

I also had same problem as "szwarek". I have WinXP 64 bit, and after turning off file system intergration(under Tools Options General) option it seem that Wuala works fine in XP64 bit now.

Roger, thank you. ;)