Page 1 of 1
vista 64 problem

Posted:
28 Nov 2009 21:03
by dckaczka
I had used version 2.4 for some time on XP without trouble. Recently built new machine with Vista 64 bit home premium version. Have tried version 2.4 but had issues that Shareaza would lock up after some period of time in use. Would still have the icon in the task bar but the program would not open. If the program window was actually open when it happened, it would stop responding. If I were to "end task" from the task manager, the icon would go away but the process would not clear in the task manager. Windows reboot was required. The reboot process would be very slow. Much longer than normal. Both the shutdown and the subsequent startup. Shareaza not set to auto start when Windows was started. I tried variuos clean loads but just lived with the issue.
Have just tried the new 2.5 version. The problems seem to be even worse. Tried just installing it. Also, tried a clean install. Any known issues going on with Vista 64 bit support?
I love the program but the problems are making it impossible to use.
Any ideas would be greatly appreciated.
Re: vista 64 problem

Posted:
28 Nov 2009 23:13
by dckaczka
Trying the latest build now (Shareaza_2.5.0.1_x64_Release_r8359_2009-11-27.exe). Initially, seemed to open and close better. Left it open for about an hour while trying to figure out how to bring in my partial downloads from before. Tried to close the application and it seemed to get stuck closing. The process is still showing in the task manager but the app looks like it is closed.
Also, any way to complete partial downloads without finding the same file again to try to start the download and then doing the merge thing? I don't know what the file names were for all the partials.
Thanks,
Re: vista 64 problem

Posted:
29 Nov 2009 08:19
by ailurophobe
IIRC, the file name is stored inside the .sd file. Also you can search G2 by hash. What happens if you just copy the partials to Shareazas downloads folder and restart Shareaza?
Still on XP, so no idea on the Vista problem other than the obvious -> Have you verified this is not caused by Anti-Virus or firewall? Or a worm.
Re: vista 64 problem

Posted:
29 Nov 2009 16:15
by dckaczka
My partials did come back when I pointed my partial folder to where they were. Didn't come back immediately but after I restarted the application a couple times. I have the firewall setup to allow shareaza (ZoneAlarm version:8.0.298.000). AVG 9 doesn't find any problems. I have not patched for the half open session thing. Didn't mind the performance hit but it wouldn't cause this would it? I am running the latest Alpha version. Seems to be a bit better, but after a period of time, it seems bogged down again and won't respond. The task manager doesn't show any issues with CPU or memory hogging though.
Re: vista 64 problem

Posted:
29 Nov 2009 20:02
by ocexyz
Please try to use Debug instead Release. This will allow you to deliver eventual bugreport which will allow devs to fix the problem. They work the same way, Debug have only added additional routines to trace if Shareaza works properly. This and bugreporting allow to fix and to develop Shareaza code to work better.
Re: vista 64 problem

Posted:
29 Nov 2009 20:45
by ailurophobe
He already is using the debug version. ("latest alpha")
The half-open limit by itself wouldn't cause this, and since you did a clean install you should have all related settings at default values -> no problem. You can check that Downloads.MaxConnectingSources in advanced settings is 8 just in case.
Re: vista 64 problem

Posted:
29 Nov 2009 21:06
by ocexyz
Re: vista 64 problem

Posted:
29 Nov 2009 21:16
by ailurophobe
LOL, never noticed somebody is doing release builds of the alpha versions.
Re: vista 64 problem

Posted:
30 Nov 2009 05:17
by dckaczka
I set it to 8. It was 28. I'll also switch to the debug. Thanks for the pointers.
Re: vista 64 problem

Posted:
30 Nov 2009 10:42
by ocexyz
Re: vista 64 problem

Posted:
30 Nov 2009 13:35
by ailurophobe
Re: vista 64 problem

Posted:
01 Dec 2009 03:07
by dckaczka
Switched to latest debug version. Downloads.MaxConnectingSources is 28 on install. Can't seems to find the ignoreSp2 setting to check if it is defaulting to FALSE and does Shareaza show 8 as being the default value.
New thing. Previews of partial downloads don't seem to be working. It processes like before but doens't play. This is for partials that were previewing with the other install.
Re: vista 64 problem

Posted:
01 Dec 2009 04:04
by kevogod
Re: vista 64 problem

Posted:
01 Dec 2009 08:11
by ailurophobe
Re: vista 64 problem

Posted:
02 Dec 2009 02:28
by dckaczka
Update. I do run Vista 64 bit SP2. Sorry, I didn't clarify that. More info on my system.
Vista Home Premium 64 bit
i7 920 with 6 GB RAM
Nvidia GeForce 9800GT
Update on symptoms. Ran Shareaza overnight last night. Minimized it overnight. When tried to maximize it in the morning it only partially maximized. Wouldn't display the whole screen. Could not get response with right click for menu on task bar area. Had to end task from task manager. Visually, the application closed. The process would not go away in the task manager process list. Had to reboot. Reboot took a long time to shutdown (probably due to the stuck process). Startup, post windows log on, seemed longer as well though it should not be impacted.
Basically, the same symptoms I had with version 2.4 and 2.5 release except I got the partial response when I tried to maximize.
Any additional ideas?
Re: vista 64 problem

Posted:
02 Dec 2009 11:48
by old_death
In order to do a real clean install, you will need to delete the registry keys from Shareaza in all user accounts where the software has been used in before doing the install of one of the v2.5.0.1 rXXXX versions.
Shareazas registry key can be found here: HKEY_CURRENT_USER\Software\Shareaza
Re: vista 64 problem

Posted:
02 Dec 2009 13:27
by dckaczka
Yep. Saw that somewhere. Only one user on the PC. When I checked after uninstalling, there where no registry entries left in that location.
Re: vista 64 problem

Posted:
02 Dec 2009 23:26
by old_death
Have you tried the v2.5.1.0 which has been released yesterday?
Re: vista 64 problem

Posted:
03 Dec 2009 05:32
by dckaczka
installed Shareaza_2.5.1.1_x64_Debug_r8380_2009-12-01 tonight. Still can't preview partials any longer. Will let run overnight and see what happens. It did stop responding after building a preview already though.
Morning. Still would not maximize properly. Did go to full screen but did not display all elements (missing menus and tabs). F5 made get that far. It started with just putting up the main screen outline with everything blank inside. After this, it seemed to hang and had to resort to end task. Process still won't clear from the task manager.
Re: vista 64 problem

Posted:
04 Dec 2009 00:17
by ocexyz
Seems there was a mistake made in compiling this one as SSE was turned on. Try newer version, please. Perhaps will work better. Have you got assert or error report from BugTrap?
Re: vista 64 problem

Posted:
04 Dec 2009 03:08
by dckaczka
I don't see a newer version. No error file has presented itself. I don't see one anywhere. Is there a certain location I should look?
Re: vista 64 problem

Posted:
04 Dec 2009 06:53
by ocexyz
Re: vista 64 problem

Posted:
06 Dec 2009 03:16
by dckaczka
Tried the newest, Shareaza_2.5.1.1_x64_Debug_r8392_2009-12-04. Same symptoms. Previews of partial downloads doesn't work as well as in 2.4. Haven't found a partial yet that will play. This version still effectively locks up after running for a period of time. Basically, it will not open from being minimized. The process will also not close from the task manager even though it has been "end tasked".
These symptoms don't seem to be unique after reading some of the other posts in the forum.
Re: vista 64 problem

Posted:
06 Dec 2009 08:45
by raspopov
Re: vista 64 problem

Posted:
06 Dec 2009 14:33
by ocexyz
Re: vista 64 problem

Posted:
06 Dec 2009 15:09
by ocexyz
deleted double post
Re: vista 64 problem

Posted:
12 Dec 2009 19:54
by dckaczka
Switched to the most recent released version, Shareaza_2.5.1.0_Win32, same problems as before. It seems to be related to how many transfers are in progress. The more that are either pending or in progress, the less time it seems to take to lock up the program.