New version just freezes and crashes now!

[punkmaister]

The previous version sometimes froze for a little while but then it resumed normal operations but this new version just freezes and crashes! Any idea why? I'm using Windows XP...

[ocexyz]

[punkmaister]

[ocexyz]

[punkmaister]

[cyko_01]

Lets think about this logically.
If you help us by trying a few debug builds:
-you will not lose any of your incomplete downloads
-you will be helping to fix the problem instead of just avoiding it
-shareaza 2.5 and debug builds have lots of new features that make it safer and easier to use
If you revert to 2.4:
-you risk losing your incomplete downloads
-other shareaza users with the same problem will not discover the awesomeness of shareaza
-you will be missing out on hundreds of new features, optimizations, and bug fixes, possibly even leaving yourself vulnerable to attacks in the future
-every time someone reverts to an older version god kills a kitten.

I suggest you take ocexyz's advice. You are not a kitten murderer are you?!!!!

[punkmaister]

[ocexyz]

Use the trick: before downgrade just install latest debug build from here and see how this can produce report showing devs what is the problem so they will have a chance to fix it to work on your system. You can do it for your own benefit: to have fixed and not crushing program adjusted to your system. And by the way what of course is not so important try new staff or not, check if it is working better for you or not.

Well there is sth that makes problem for you. If you will not report it, it will not be fixed. You can report it only when using debug build. Also, take this as extra bonus, it can occur that this problem has already been fixed in debugs - in such a case debug will be more stable for you. And there are many ppl using debug builds on everyday as new versions are expected to be published in a time - as we are just open source only. And that new version will have just what is in debug build. Difference is that new versions of debug builds are published almost everyday or every few days, but official releases only 2-3 times in year when devs will decide that debug build is matured enough to become official realise, and it will not be changed until next new release - simply because it works for most of users properly. All, like you, who have problems we are ready to help and support and we provide more fixed code in form of debug builds. But we can't force anyone to use more developed code when one is afraid of "debug build" strange name.

Logical consequence of above for me is try debug build please and let us know effects. And deliver eventual error report.

And I don't think I can add anything more to this. More posts from you like this will not change anything as there is no any bugreport from you (which can be created with debug build only) and besides fact that at your machines happens crash we do not now anything, so we CAN'T do anything. When you will accept this fact perhaps you will try debug build and needed fixing can be coded, if needed at all. That is all from me about this. Think it over please and consider trying latest debug build.

[punkmaister]

Darn it I nearly forgotten I do have Microsoft Visual Studio installed in my computer and whenever a program crashes it gives me the option of running the Debugger, now if I where to choose the option of running the Debugger and sending you a screencap of the code is showing etc, could that help?

[ocexyz]

[ailurophobe]

Also, the error might be one of those that gets fixed by installing anyway. A corrupted executable or something like that.