Any slskQT build crashes for unknown reason

Submitted by lucian.cebo on Fri, 05/27/2011 - 14:00
Forums: 
Soulseek General Discussion

I recently found out about slskQT and decided to give it a try. I loved of the direction it seemed to be going to I stuck with it. It worked very well until a couple of days ago, it just randomly started crashing.
I've tried different builds, trying seeing maybe it's because of the downloads of something i did in the program, but couldn't find any pattern.
I tried with 0 downloads, with lots of downloads, with/without chats, no chat rooms open, no uploads, nothing...it seems though it takes different times for each crash to occur.

What could it be, what can i do to help fix this, does anyone else have this issue?

running win 7, 64 bit, on asus notebook
intel i5
4g ram

crash report?
Problem signature:
Problem Event Name: APPCRASH
Application Name: SoulseekQT.exe
Application Version: 0.0.0.0
Application Timestamp: 4dd37b3d
Fault Module Name: libgcc_s_dw2-1.dll
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 4a404122
Exception Code: c0000094
Exception Offset: 00003c4f
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt

Submitted by Nir on Fri, 05/27/2011 - 15:07.

Let me see what I can do about getting the client to come up with a crash report.

Submitted by Nir on Sat, 05/28/2011 - 01:52.

Okay, well, taking another look at the crash report you've posted, it looks as if the crash might have occurred in one of the Qt DLLs rather than the application itself. If that's the case, I can try and bundle the executable with different versions of the Qt libraries. But first, there might be a way to make sure by producing a more detailed crash report. If you're up to it, here's what you need to do:

  1. Download and unzip drmingw-0.4.4.zip.
  2. Open a command line window, navigate to the folder you've extracted above, and install Dr. MingW as your machine's default just-in-time debugger by typing "drmingw -i" without the quotes. You can later remove it by typing "drmingw -u".
  3. Download and use this version of the SoulseekQT client: SoulseekQT - drmingw.zip. When the client crashes, you should be offered an option to debug it. Select it and a Dr. MingW window should open and produce a detailed crash report. One you have it, post it here. If all works as it should, this should give me a good idea of just what's going on with the client on your machine.

Thanks, Nir

Submitted by lucian.cebo on Sat, 05/28/2011 - 19:04.

I can't seem to install it, i don't get a message saying it was installed, i tried it either way but i didn't get a drmingw window after it crashed.
this is what i wrote in cmd (the folder is on the desktop)
C:\Users\Luka>Desktop\drmingw-0.4.4\drmingw -i
where did i go wrong? :)
i also tried just executing the file, nothing...

Submitted by Nir on Sat, 05/28/2011 - 21:30.

Does it tell you Dr. Mingw has been installed as the default application debugger after you type drmingw -i? Maybe you need to run the command prompt in administrator mode. Press the Windows button and type "cmd" in the search programs and files bar. Then right-click cmd.exe and choose run as administrator. Maybe Dr. Mingw will install properly that way.

Submitted by lucian.cebo on Sun, 05/29/2011 - 18:31.

yep, that worked :)
http://www.text-upload.com/read.php?id=84244&c=9104789

Submitted by Nir on Sun, 05/29/2011 - 18:57.

Perfect! I'll take a look at it later tonight and see if I can't post a fix here. Thanks!

Submitted by Nir on Mon, 05/30/2011 - 00:34.

I think I got it. The crash had to do with the client incorrectly handling peer connections that aren't initialized properly. Oddly enough this never triggered at any time when I was using the client myself. I'm tempted to say this is the result of someone tampering with your listening port, but it may be indicative of some larger problem with the client. At any rate, it should be fixed in this build: SoulseekQT nightly build 5/29/2011.zip.

Thanks for helping me locate this bug!

roomx's picture

Submitted by roomx on Sat, 05/28/2011 - 07:48.

1. Program not showing shares. I managed to share, but the number of files don't show up.
2. How do I add users to list?

Search function is really neat. Looking forward to seeing more of that..

Submitted by Nir on Sat, 05/28/2011 - 15:02.

roomx, you need to create a new forum topic for this. this thread is about the crash reporter.

aniamiti's picture

Submitted by aniamiti on Tue, 08/02/2011 - 00:29.

Hi!
I got this message upon trying to connect:
"[11:27:59] Initializing UPnP
[11:28:07] No device list found during discovery. miniupnp error code: 0"
I know this might sound trivial, but i do suggest a step-by-step guide to properly configuring ports. this should come handy :)
great work, keep it real!

Submitted by www.MetalLore.org on Tue, 08/16/2011 - 16:19.

After start soulseek (build SoulseekQt nightly build 8/9/2011) it is felt that the system works more slowly.
The program consumes nearby 300mb memories, and CPU loading constantly skips. And periodically takes off \ crush.
Considering that i have 4 core and 8gb, it isn't normal. win7 x64.

i have installed drmingw, now waiting to crush.

Submitted by Fritz14 on Thu, 06/25/2015 - 23:52.

Thanks for the information. Nice post.

purchase soundcloud downloads