Soulseek freezing/crashing/stops working constantly... Help?

Submitted by marshmallowc on Sat, 03/19/2016 - 09:59
Forums: 
Soulseek General Discussion

I've had this problem for years now without any improvement. Soulseek always crashes and freezes constantly. It happens with every version I try (even the latest version, which I have). I describe what happens in detail here: https://rateyourmusic.com/board_message?message_id=5531305&find=5531305&...

Any help would be appreciated.

Submitted by Nir on Mon, 03/21/2016 - 18:49.

What version of the client are you currently using? Also, are you using AVG?

Submitted by sammy123 on Mon, 03/21/2016 - 23:20.

Hello marshmallowc
have U tried running analyzer like Process explorer or process monitor in the background. As Nir has about 100k Users in Q, most use the native SLSKqt client, there are a lot of happy users on three different OS, so the problem must be on your client.
What slskqt is quite messy about is when it's doing something (Queue updating, providing search results, .....) and when you switch to another SLSK function and click a few times on the client it could drop (crash) you down. That's not SLSK specific, but Browsers have the same behavior.
When using e.g. Procexp64 then look at the CPU load + Memory needs at that time when the crash happens. Depending on your CPU (HT active or how many cores) a fully loaded CPU core (SLSKqt only uses one) can happen already when you have 8% load (6 cores + HT active) which seems rather a low load for a big CPU. When you share a lot or try to DL a lot Queue could get out of memory as well. AntiVirus Programs could interfere a lot into the fast changing Queue Order and stall the SLSK client (happens with databases a lot).
Cheers

Submitted by spawnster on Thu, 04/07/2016 - 10:39.

I'm using the 2015.6.12 build and it keeps crashing on Windows 7 64-bit. I've tried many things to figure out what is going but have yet to find an answer. Keep getting Microsoft Runtime Errors. What I've noticed in going through the different thread on here, is that a lot of people have had this problem. I'm sure most have been able to fix it, unfortunately I'm not one of them.
Have tried DrMing to generate a crash report, to deleting anything with Runtime or C++, to performing a clean reboot. I'm hoping there's a simple solution to this problem. What I'd really like is for a dumbed down solution. Stuff I tried is over my head.
Thanks in advance.

Submitted by sammy123 on Fri, 04/08/2016 - 10:15.

Hi spawnster,
as mentioned before:
What slskqt is quite messy about is when it's doing something (Queue updating, providing search results, .....) and when you switch to another SLSK function and click a few times on the client it could drop (crash) you down. That's not SLSK specific, but Browsers have the same behavior.
So C++ errors are the normal way Windows reports a terminated app, nothing really special. Try the different profile. Maybe your config file is damaged when redoing his logs?!
Cheers

Submitted by spawnster on Fri, 04/08/2016 - 11:20.

Hi sammy123.
Thanks for your response. However I don't think what you mention is the problem. Soulseek crashes when just downloading. I have since learned that it crashing has nothing to do with the program. Most likely something on my computer. What that is, I don't know.

Submitted by sammy123 on Sat, 04/09/2016 - 07:07.

Hi
this forum is far beyond PC problems. The causes range from software problems (e.g. driver problems) down to hardware problems (often HD/Mainboard/RAM). The one who installed it should be the one to contact as he/she should know his (sold) hardware best. Else contact a nearby PC shop and ask for help of instability. There's no testtool who points exactly (or even near) the spot what's wrong. It's all up to experience and good diagnosing.
Cheers

Submitted by spawnster on Sat, 04/09/2016 - 07:44.

This thread is for Soulseek crashing or freezing. Crashing is what my problem is. I'm sure it's a software problem since hardware didn't change from the last time I was using a stable version of the program.
In any case I'm going to be getting some help from someone off of here.

Submitted by Nir on Tue, 04/12/2016 - 16:50.

Hey Steven, would you mind trying this build when you have the time?

https://www.dropbox.com/s/z438uu18b4ktu2h/SoulseekQt-2016-4-12.7z?dl=0

It's integrated with the latest TagLib library, I tested it with the folder that was causing the crash on your machine and it goes through without any problem. I'm wondering if it'll have problems with any of your other files.

Submitted by nnsxnks on Mon, 05/09/2016 - 10:36.

This is also about Soulseek freezing.

So, SoulSeek was always working fine for me. Now it started to freeze right after the beginning, I have barely time to do one click before it freezes. I think that it is because one guy just decided to download hundreds of files at once and SoulSeek cannot handle the queue. The question is - how can I stop him from doing so when SoulSeek freezes instantly?

Thanks!

Submitted by sammy123 on Mon, 05/09/2016 - 22:08.

Hi nnsxnks
first: SLSKqt handles even a few thousand without problems, so that's not the cause. As it seems to me the config file got corrupted and freezes when SLSK works thru it to get ready. The config files are named soulseek-client.dat....lotsofnumber. Rename them or move them to a different location so SLSK could start again. If that works you might have exported on some time your settings, else you have to start (configuring) from scratch. Most corruptions I've seen/diagnosed are from crashes of SLSK when writing the config files (missing pieces) or when upgrading from one version to another without an proper export/import procedure. Cause is some older settings did not work with newer ones.
Cheers

Submitted by XstaticProcess on Sun, 05/15/2016 - 16:19.

Since I updated to latest version this week I'm having the same freezing problem. I am able to use soulseek for about 3 to 5 min. then it just freeze.
If I try forcing it to close I'm not able to use soulseek anymore unless I restart the system.

Submitted by sammy123 on Mon, 05/16/2016 - 06:13.

Hi XstaticProcess,
then a downgrade to the older version would be the solution. It would be great if you name the version you used so other OSX users can avoid them.
Cheers