App no longer opens - Windows 10, client 2019.7.22

405 views
Skip to first unread message

Gavan O'Connor-Risch

unread,
Feb 15, 2023, 7:05:50 PM2/15/23
to Soulseek Technical Discussion
Window will load when app starts, think for a few seconds (username displays in window title) then crash. Have tried uninstall and reinstall, no change.

Have also run sfc /scannow a few times, first time it did report some fixes, second time no fixes.

Faulting application name: SoulseekQt.exe, version: 0.0.0.0, time stamp: 0x5d37aac9
Faulting module name: libstdc++-6.dll, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x40000015
Fault offset: 0x0000000000020197
Faulting process id: 0x8
Faulting application start time: 0x01d94199e63b75ec
Faulting application path: C:\Program Files (x86)\SoulseekQt\SoulseekQt.exe
Faulting module path: C:\Program Files (x86)\SoulseekQt\libstdc++-6.dll
Report Id: 22f2e247-6aae-432a-95d6-e58580fbed78
Faulting package full name:
Faulting package-relative application ID:

Fault bucket 1721920384559154877, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SoulseekQt.exe
P2: 0.0.0.0
P3: 5d37aac9
P4: libstdc++-6.dll
P5: 0.0.0.0
P6: 00000000
P7: 40000015
P8: 0000000000020197
P9:
P10:  

Nir Arbel

unread,
Feb 15, 2023, 9:18:21 PM2/15/23
to Soulseek Technical Discussion

Gavan O'Connor-Risch

unread,
Feb 18, 2023, 6:24:56 PM2/18/23
to Soulseek Technical Discussion
Hi,

Thanks for the new build!
Looks like more of the same - although with this build the window doesn't show before crashing

Faulting application name: SoulseekQt.exe, version: 0.0.0.0, time stamp: 0x63ca7dc5

Faulting module name: libstdc++-6.dll, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x40000015
Fault offset: 0x0001f9c3
Faulting process id: 0x5824
Faulting application start time: 0x01d943efc8daf4d5

Faulting application path: C:\Program Files (x86)\SoulseekQt\SoulseekQt.exe
Faulting module path: C:\Program Files (x86)\SoulseekQt\libstdc++-6.dll
Report Id: 60634f03-cdfa-447f-8022-8488c7a2b402

Faulting package full name:
Faulting package-relative application ID:

Fault bucket 2258346689060451450, type 1

Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: SoulseekQt.exe
P2: 0.0.0.0
P3: 63ca7dc5

P4: libstdc++-6.dll
P5: 0.0.0.0
P6: 00000000
P7: 40000015
P8: 0001f9c3
P9:
P10: 

Nir Arbel

unread,
Feb 19, 2023, 4:33:33 AM2/19/23
to Soulseek Technical Discussion
If you're up for it, we can try figuring out where in the code the crash happens by running a special debug build. You'd have to first install Dr. MingW as outlined here:


And then run this special build that includes debug symbols:

Hopefully when it crashes again it'll pop up a window with a bunch of text in it that might show where in the code it's happening. If you get it just cut/paste the crash log and post it here or send it to me privately.

Gavan O'Connor-Risch

unread,
Feb 20, 2023, 7:13:19 PM2/20/23
to Soulseek Technical Discussion
Hi Nir,

Thanks for the help so far. I think this is the output you're after?

Registers:
eax=00000102 ebx=00000006 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=76a9586c esp=0e78e108 ebp=0e78e178 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202

AddrPC   Params
76A9586C 00000000 00000000 FFFFFFFF  win32u.dll!_NtUserMsgWaitForMultipleObjectsEx@20+0xc
76B4C71A 00000000 00000000 FFFFFFFF  USER32.dll!RealMsgWaitForMultipleObjectsEx+0x7a
76B4C64C 00000000 00000000 FFFFFFFF  USER32.dll!_MsgWaitForMultipleObjectsEx@20+0x4c
68CB02EE 0DEC1ED8 00000000 00000024  Qt5Core.dll!QEventDispatcherWin32::processEvents+0x34e
68C543BB 00000000 0DEC4438 0E78FF68  Qt5Core.dll!QEventLoop::exec+0x12b
68AA0097 00000000 0DEC1ED8 00000000  Qt5Core.dll!QThread::run+0x57
68AA0902 00000000 75EC00F9 0DEBFB60  Qt5Core.dll!QThread::qt_metacall+0x662
75EC00F9 0DEBFB60 5C29782A 00000000  KERNEL32.DLL!@BaseThreadInitThunk@12+0x19
76F47BBE FFFFFFFF 76F68D24 00000000  ntdll.dll!__RtlUserThreadStart+0x2f
76F47B8E 68AA0810 0DEBFB60 00000000  ntdll.dll!__RtlUserThreadStart@8+0x1b

Registers:
eax=00000102 ebx=00000006 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=76a9586c esp=11eae108 ebp=11eae178 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202

AddrPC   Params
76A9586C 00000000 00000000 FFFFFFFF  win32u.dll!_NtUserMsgWaitForMultipleObjectsEx@20+0xc
76B4C71A 00000000 00000000 FFFFFFFF  USER32.dll!RealMsgWaitForMultipleObjectsEx+0x7a
76B4C64C 00000000 00000000 FFFFFFFF  USER32.dll!_MsgWaitForMultipleObjectsEx@20+0x4c
68CB02EE 11337C20 00000000 00000024  Qt5Core.dll!QEventDispatcherWin32::processEvents+0x34e
68C543BB 00000000 0EF2D8B8 11EAFF68  Qt5Core.dll!QEventLoop::exec+0x12b
68AA0097 00000000 11337C20 00000000  Qt5Core.dll!QThread::run+0x57
68AA0902 00000000 75EC00F9 0EE63264  Qt5Core.dll!QThread::qt_metacall+0x662
75EC00F9 0EE63264 43BB782A 00000000  KERNEL32.DLL!@BaseThreadInitThunk@12+0x19
76F47BBE FFFFFFFF 76F68D24 00000000  ntdll.dll!__RtlUserThreadStart+0x2f
76F47B8E 68AA0810 0EE63264 00000000  ntdll.dll!__RtlUserThreadStart@8+0x1b

Registers:
eax=00000000 ebx=0b89e0b8 ecx=00000000 edx=00000000 esi=0b89e0b8 edi=0b891d40
eip=76f5482c esp=0c08fdb4 ebp=0c08ff70 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206

AddrPC   Params
76F5482C 000000D8 0B89DEF8 00000010  ntdll.dll!_NtWaitForWorkViaWorkerFactory@20+0xc
76F15C60 0B891D40 75EC00E0 0C08FFDC  ntdll.dll!TppWorkerThread+0x2a0
75EC00F9 0B891D40 5E59782A 00000000  KERNEL32.DLL!@BaseThreadInitThunk@12+0x19
76F47BBE FFFFFFFF 76F68D24 00000000  ntdll.dll!__RtlUserThreadStart+0x2f
76F47B8E 76F159C0 0B891D40 00000000  ntdll.dll!__RtlUserThreadStart@8+0x1b

Registers:
eax=00000000 ebx=0b8955b8 ecx=00000000 edx=00000000 esi=0b8955b8 edi=0b891d40
eip=76f5482c esp=0be4fdb4 ebp=0be4ff70 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206

AddrPC   Params
76F5482C 000000D8 0B8953F8 00000010  ntdll.dll!_NtWaitForWorkViaWorkerFactory@20+0xc
76F15C60 0B891D40 75EC00E0 0BE4FFDC  ntdll.dll!TppWorkerThread+0x2a0
75EC00F9 0B891D40 59B5782A 00000000  KERNEL32.DLL!@BaseThreadInitThunk@12+0x19
76F47BBE FFFFFFFF 76F68D24 00000000  ntdll.dll!__RtlUserThreadStart+0x2f
76F47B8E 76F159C0 0B891D40 00000000  ntdll.dll!__RtlUserThreadStart@8+0x1b

Registers:
eax=00000000 ebx=0b893e48 ecx=00000000 edx=00000000 esi=0b893e48 edi=0b891d40
eip=76f5482c esp=0bc4fdb4 ebp=0bc4ff70 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000206

AddrPC   Params
76F5482C 000000D8 0B893C88 00000010  ntdll.dll!_NtWaitForWorkViaWorkerFactory@20+0xc
76F15C60 0B891D40 75EC00E0 0BC4FFDC  ntdll.dll!TppWorkerThread+0x2a0
75EC00F9 0B891D40 5995782A 00000000  KERNEL32.DLL!@BaseThreadInitThunk@12+0x19
76F47BBE FFFFFFFF 76F68D24 00000000  ntdll.dll!__RtlUserThreadStart+0x2f
76F47B8E 76F159C0 0B891D40 00000000  ntdll.dll!__RtlUserThreadStart@8+0x1b

Registers:
eax=00000102 ebx=00000006 ecx=00000000 edx=00000000 esi=00000000 edi=00000000
eip=76a9586c esp=11cae108 ebp=11cae178 iopl=0         nv up ei pl nz na pe nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000202

AddrPC   Params
76A9586C 00000000 00000000 FFFFFFFF  win32u.dll!_NtUserMsgWaitForMultipleObjectsEx@20+0xc
76B4C71A 00000000 00000000 FFFFFFFF  USER32.dll!RealMsgWaitForMultipleObjectsEx+0x7a
76B4C64C 00000000 00000000 FFFFFFFF  USER32.dll!_MsgWaitForMultipleObjectsEx@20+0x4c
68CB02EE 1130A900 00000000 00000024  Qt5Core.dll!QEventDispatcherWin32::processEvents+0x34e
68C543BB 00000000 0EF2E3F8 11CAFF68  Qt5Core.dll!QEventLoop::exec+0x12b
68AA0097 00000000 1130A900 00000000  Qt5Core.dll!QThread::run+0x57
68AA0902 00000000 75EC00F9 0EEB58EC  Qt5Core.dll!QThread::qt_metacall+0x662
75EC00F9 0EEB58EC 439B782A 00000000  KERNEL32.DLL!@BaseThreadInitThunk@12+0x19
76F47BBE FFFFFFFF 76F68D24 00000000  ntdll.dll!__RtlUserThreadStart+0x2f
76F47B8E 68AA0810 0EEB58EC 00000000  ntdll.dll!__RtlUserThreadStart@8+0x1b

Registers:
eax=00000000 ebx=00000000 ecx=00000000 edx=00000000 esi=00000003 edi=77005b40
eip=76f52dbc esp=0b85f26c ebp=0b85f340 iopl=0         nv up ei pl nz na po nc
cs=0023  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00200206

AddrPC   Params
76F52DBC FFFFFFFF 00000003 18B00298  ntdll.dll!_NtTerminateProcess@8+0xc
76F3D79D 00000003 77E8F3B0 FFFFFFFF  ntdll.dll!RtlExitUserProcess+0xbd
75EC5992 00000003 0B85F3A4 76766687  KERNEL32.DLL!_ExitProcessImplementation@4+0x12
76766127 00000003 F7994419 18B00298  msvcrt.dll!___crtExitProcess+0x17
76766687 00000003 00000001 00000000  msvcrt.dll!doexit+0x135
767660C1 00000003 00010001 0B85F588  msvcrt.dll!__exit+0x11
7675B768 19EE15F8 00000001 00000002  msvcrt.dll!_abort+0xe8
6FE5F9C3 0B85F91C 00000001 00000004  libstdc++-6.dll!__gnu_cxx::__verbose_terminate_handler+0x163
00477E94 0B85FCF0 00000001 0B85FCC0  SoulseekQt.exe!DataSaver::load+0x394  [C:/git/build-SoulseekQT-Desktop_Qt_5_12_12_MinGW_32_bit-Release/../SoulseekQt/DataSaver.cpp @ 361]
0041BF82 00000000 00000000 006451C0  SoulseekQt.exe!MainWindow::init+0x66f2  [C:/git/build-SoulseekQT-Desktop_Qt_5_12_12_MinGW_32_bit-Release/../SoulseekQt/mainwindow.cpp @ 383]
00401AA1 00000001 0C70D878 0B8A0B58  SoulseekQt.exe!qMain+0x4d1  [C:/git/build-SoulseekQT-Desktop_Qt_5_12_12_MinGW_32_bit-Release/../SoulseekQt/main.cpp @ 80]
005CFA92 48A7A46A AA18F670 04000000  SoulseekQt.exe!WinMain@16+0x142


Nir Arbel

unread,
Feb 22, 2023, 2:22:35 PM2/22/23
to Soulseek Technical Discussion
Looks like it's crashing when it's trying to load your configuration data. It might have become corrupted somehow. The configuration files are usually in a folder named C:\Users\[Windows username]\AppData\Local\soulseekQt\1 or something similar. They should contain a number of files named soulseek-client.dat.[timestamp], you can use a utility like Search Everything and look for soulseek-client.dat.*. If you delete them you should be able to run the client and configure everything from scratch, but if you send them to me  before you delete them I'd like to try to reproduce the problem on my side.

Gavan O'Connor-Risch

unread,
Feb 22, 2023, 10:46:48 PM2/22/23
to Soulseek Technical Discussion
Thanks, it's loading now with a fresh config - I still have a lot of users saved from my original client, so I think I'll be ok from here

Thanks so much for the help

Gavan O'Connor-Risch

unread,
Feb 22, 2023, 10:50:15 PM2/22/23
to Soulseek Technical Discussion
Here is one of the config files btw

config.zip

Nir Arbel

unread,
Feb 24, 2023, 12:49:07 AM2/24/23
to Soulseek Technical Discussion
Thank you!
Reply all
Reply to author
Forward
0 new messages