Was working perfect for weeks, now locking up

Submitted by mybitterness on Wed, 01/02/2013 - 06:04
Forums: 
Soulseek General Discussion

I had been using the 12-2-12 release of QT, and it had been working beautifully for a few weeks! Today, I tried running the program and it would freeze within 20 seconds of it being open. Had to ctrl alt del to exit out of it. I also noticed that it was shooting the disk usage up to 100%, which I never noticed it doing before today. Like I said, it had been running smoothly and perfect. Anyway, tried rebooting the system, uninstalling and reinstalling, having tried several different release versions. Any idea why QT suddenly hates me? I haven't really made any changes to my system at all in the last few weeks. Any insight on this problem would be wonderful. Thanks for all the hard work you do!

Submitted by Nir on Wed, 01/02/2013 - 21:43.

Try this utility:

http://www.nirsoft.net/utils/process_activity_view.html

Even though I have a 64-bit operating system the 32-bit was the one that worked for me, maybe because the SoulseekQt process is 32-bit. Once you attach the utility to SoulseekQt it'll tell you exactly which files it's accessing and how. If you see something notable there, post it here, or just post a screenshot of what you end up getting after a while.

Thanks! Nir

Submitted by sysmaster01 on Sat, 01/05/2013 - 06:57.

As reported by me in another thread (though no replies there yet). Exactly the way you describe it, mybitterness.

I have a stupid one-liner that at least keeps SlskQt operable:

$ killall SoulseekQt-12-2-2012; sleep 3; ./SoulseekQt-12-2-2012

I just have to repeat this procedure until the insane 100% CPU usage stops and I can move around in the tabs.
Max tries have been 10 so far, but usually it would work after the 3rd try (average) ;)

Submitted by Nir on Sat, 01/05/2013 - 18:56.

You're saying you can't even kill the process? Are you on Linux 32 or 64 bit?

Submitted by sysmaster01 on Wed, 01/09/2013 - 13:08.

32bit! Linux 3.3.7, if that matters. And yes I can kill the process; by means of kill/pkill/killall, that is, though. Doing it via the 'X', leaves me back a zombie in process list that I have to kill manually (window itself would close, though)

Nir, it might be due to major changes/amendments/improvements(?) in the config file you've made through the months? Because yesterday, by initiating a manual user upload, I was able to hand-trigger the 100% CPU problem (Slsk froze).

Eventually, I decided to hit the emergency switch.
Using a VANILLA config file made everything worked fine again; however, I will have to redo all my settings like colors (OH NO!!) and share folders setup. Having all of that data stuffed into one proprietary, non-externally-editable file may induce problems (obviously). Let alone that this mush of binary gobbledigook will make hunting for data corruption virtually impossible.

I wish this will be changing sometime.

Submitted by Giamixflix on Mon, 01/07/2013 - 07:17.

The same thing happened to me, except the problem about the 100% CPU usage. I tried to re-install the program but it didn't solve anything. Maybe is a problem because I'm using windows 8?

Submitted by Nir on Mon, 01/07/2013 - 20:58.

There might be something you can do to help me diagnose this problem. Download this version of the client:

http://www.slsknet.org/SoulseekQt/Windows/SoulseekQt-Profiling.zip

Extract the SoulseekQt-Profiling folder contained within, and run SoulseekQt.exe in that folder. Let the client get to a point where it takes 100% CPU and ideally let it keep running for a while longer. Then close it. A file named gmon.out should appear in the SoulseekQt-Profiling folder. Once you have it send it to the e-mail address I messaged you in private. This might have a record of what's using up the CPU on your machine.

Thanks, Nir

Submitted by sysmaster01 on Thu, 01/10/2013 - 09:42.

neat! Nir, may I have one of these too for Linux then, please? :)
Because I still have the old .Soulseek data file preserved as-is, so I can joyfully reproduce the 100% CPU problem whenever I want to ;)
Merely gdb is not as ... er ... talkative as I want it to ;)

Submitted by Nir on Wed, 01/09/2013 - 14:25.

Absolutely, I'm at work right now but I'll link to a version for Linux 32-bit as soon as I can.

Thanks, Nir

Submitted by sysmaster01 on Thu, 01/10/2013 - 09:43.

Coolish! So I had better not touch that data file now, to ensure that the profiler in your upcoming build won't be out of work :P

Ta' much.