Same here it just instantly goes in not responding and then just closes.

LAUVz on 6 May 2019

👍2 🚀1

Yeah it's broken.

LittleVulpix on 6 May 2019

Same here x64
w10 1809 latest patch level

infr-automation on 6 May 2019

Maybe unimportant but which win 10 version? I'm still on 1803, no problems with starting 4.1.6.

thalieht on 6 May 2019

1903

christianwells11 on 6 May 2019

1703

LittleVulpix on 6 May 2019

Same here with me (1903)
Workaround:
run qbittorent in administrator and it works.

Neocridas on 6 May 2019

👍5 😄1 👎1

Same here, work around did't work.

32 bit versions is working well.

malinwa001 on 6 May 2019

Mine already runs as admin, and well, it doesn't run. For the time being, back to 4.1.5 which works no problem.

LittleVulpix on 6 May 2019

👍2

I am using Win 10 Ent x64 build 1903.18362.86 after i updated to QBT 4.1.6 it was working for sometime but every time i had start it twice as the first time it was crashing. But now it opens for few seconds and then crashes.

njscorpion on 6 May 2019

I suspect it is the same as https://github.com/qbittorrent/qBittorrent/issues/9667#issuecomment-464445025
So you'll need to edit C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini and change DownloadTrackerFavicon=true to DownloadTrackerFavicon=false save and restart qbt.

Note: You only need to edit the ini if you upgraded from older qbt version. If you did a clean install then no editing is required.

Chocobo1 on 6 May 2019

👍13

Having the same issue, with win 10 (1903) x64.

@Chocobo1 suggested solution does not working for me.

MoralisRubric on 6 May 2019

@Chocobo1 suggested solution does not working for me too. fixes by back to 4.1.5 🙃

Cologler on 6 May 2019

I'm having the same issue in Windows 7 x64. qBT 4.1.6 starts loading, takes the usual long time to load all my torrents, then "Application not responding" without even painting the window. Went back to 4.1.5 although the fix for checking all files at the same time was very important for me.

TiagoJSilva on 6 May 2019

It doesn't even want to install on my WIndows 10 64 bit system. I get a "can't write file.exe" error.

legithubuser on 6 May 2019

I have 2 VMs running Windows 10 on it. Both are very similar configuration and same version of windows. Both just updated to 4.1.6 x64 and both had crashes right after startup. For one of them, the fix suggested by @Chocobo1 worked perfectly. For the other one, the fix or running as administrator has not worked. I'm downgrading now. The exception from Event Viewer does not provide any useful information:
Faulting application name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5ccf3300 Faulting module name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5ccf3300 Exception code: 0xc0000005 Fault offset: 0x0000000000aa83e0 Faulting process id: 0x1500 Faulting application start time: 0x01d5040911ae259a Faulting application path: C:\Program Files\qBittorrent\qbittorrent.exe Faulting module path: C:\Program Files\qBittorrent\qbittorrent.exe Report Id: 24aef07f-baa1-4f58-ac25-3d713e5f54e2 Faulting package full name: Faulting package-relative application ID:

phucyall on 6 May 2019

My issue was solved with the favicon fix in qbittorrent.ini

TiagoJSilva on 6 May 2019

Those still having crashes can you try the following build?
Just extract and run in any folder. (or you can overwrite the installed files)

Link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581.7z

sledgehammer999 on 6 May 2019

Is there source for this build / commits? One can never be too cautious running random stuff from the internet... Thanks!

LittleVulpix on 6 May 2019

@LittleVulpix in case you didn't know I am the admin. I make the official builds and releases.
This particular build is the exact same source as 4.1.6, but with the /guard:cf compiler/linker option disabled. (I have run into issues in the past with it).
If this doesn't work, I'll have to try something else.

sledgehammer999 on 6 May 2019

@sledgehammer999 I didn't; my bad. I tried it in my test system, but the problem is the same. It also takes a very long time to init as opposed to 4.1.5 which launches in a few seconds. 4.1.6 takes about 30 seconds and then it crashes.

LittleVulpix on 6 May 2019

Can you try the following build? It is v4.1.5 but with all the new libs used in 4.1.6. I am trying to figure it if the problem is in the new qbt code or in the new libs.
Link: https://builds.shiki.hu/temp/qbittorrent_4.1.5_x64_for_issue_10581.7z

sledgehammer999 on 6 May 2019

That one crashes as well. Though, it just "disappears silently". I don't get a windows "crash" message anymore. Nonetheless, it does not work.

LittleVulpix on 6 May 2019

@sledgehammer999 both the files you attached are still causing crashes on my machine. Looking at the crash report there's nothing even remotely useful in there. If you have a debug build you want me to try I'll be more than happy to test it.

phucyall on 6 May 2019

Looking at the crash report

Wait! You get a window of qbt with a stacktrace? If yes, can you post it?

sledgehammer999 on 6 May 2019

I think he means the windows "reliability" crash report, stuff like:

Problem signature
Problem Event Name: APPCRASH
Application Name: qbittorrent.exe
Application Version: 4.1.5.0
Application Timestamp: 5cd067b0
Fault Module Name: qbittorrent.exe
Fault Module Version: 4.1.5.0
Fault Module Timestamp: 5cd067b0
Exception Code: c0000005
Exception Offset: 0000000000aa8110
OS Version: 10.0.15063.2.0.0.256.48
Locale ID: 2057
Additional Information 1: 4b4d
Additional Information 2: 4b4d9c387d9719f8e22f494826099edf
Additional Information 3: 7bc7
Additional Information 4: 7bc7fc03d52134064a3b598b6489e1ca

Which, as he noted, tells you nothing.

LittleVulpix on 6 May 2019

New build. It is v4.1.6 but with the libtorrent and boost version used in v4.1.5.
(that libtorrent version fails to build with latest boost)
Link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v2.7z

sledgehammer999 on 6 May 2019

This crashes as well.

LittleVulpix on 6 May 2019

This crashes as well.

Same. And yes I meant the same crash report that @LittleVulpix posted.

phucyall on 6 May 2019

_Yeah, I tested your new build sledgehammer999 and it doesn't work either._

Oh, never mind, there was a Second version, the first one crashed even faster than the normal 4.1.6.
The second version also crashes.

Reverted back to 4.1.5 - it works.

Sleepovers on 7 May 2019

Unofficial test build
qBt 4.1.6 with Qt 5.12.3, Boost 1.70, Libtorrent 1.13, OpenSSL 1.0.2r
https://drive.google.com/open?id=1lKHIgCEEtHQNfhD_dfo1viBfk1N5Rswx

c0re100 on 7 May 2019

Running as administrator worked in my case! ;)
Windows 10 x64 (build 1709)
qBittorrent v4.1.6 original release

Domy81 on 7 May 2019

👍1

This build is v4.1.6 but uses the newer Qt 5.12.3.
link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z

NOTE: All my test builds( and original 4.1.6) use openssl 1.1.1b. While the original 4.1.5 build used the 1.0.x series. That's the next thing I am going to change if this build doesn't work.

sledgehammer999 on 7 May 2019

👍6

It's not a good idea to run it as admin. It shouldn't require such privileges. If it does, then there's something wrong.

sledgehammer999 on 7 May 2019

This build is v4.1.6 but uses the newer Qt 5.12.3.
link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z

NOTE: All my test builds( and original 4.1.6) use openssl 1.1.1b. While the original 4.1.5 build used the 1.0.x series. That's the next thing I am going to change if this build doesn't work.

I remember qBt 4.1.4 crash too if using openssl 1.1, so i think openssl 1.1 is the main problem.
Btw original 4.1.6 won't crash on my windows 10, maybe my vm is clean profile?
FYI: #9865

c0re100 on 7 May 2019

This https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z works for me. No crash.

LittleVulpix on 7 May 2019

👍3

I suspect it is the same as #9667 (comment)
So you'll need to edit C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini and change DownloadTrackerFavicon=true to DownloadTrackerFavicon=false save and restart qbt.

Note: You only need to edit the ini _if_ you upgraded from older qbt version. If you did a clean install then no editing is required.

Came here because i was having random crashes with 4.1.6 but on windows 7 x64.
Setting DownloadTrackerFavicon=false solved it for me.

joder666 on 7 May 2019

I suspect it is the same as #9667 (comment)
So you'll need to edit C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini and change DownloadTrackerFavicon=true to DownloadTrackerFavicon=false save and restart qbt.

Note: You only need to edit the ini _if_ you upgraded from older qbt version. If you did a clean install then no editing is required.

This works for me.

RabidWolf on 7 May 2019

🎉1 👍1

DownloadTrackerFavicon=false fixed it. Thanks, internet! :)

jojoTheBearded on 7 May 2019

This build is v4.1.6 but uses the newer Qt 5.12.3.
link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z

NOTE: All my test builds( and original 4.1.6) use openssl 1.1.1b. While the original 4.1.5 build used the 1.0.x series. That's the next thing I am going to change if this build doesn't work.

This one worked for me. None of the previous suggestions/builds worked for me.

mamefan1945 on 7 May 2019

DownloadTrackerFavicon=false fixed the crashing for me on 4.1.6, but it's MUCH slower than 4.1.5 is.
I had to roll back.

Unimatrix0 on 7 May 2019

I suspect it is the same as #9667 (comment)
So you'll need to edit C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini and change DownloadTrackerFavicon=true to DownloadTrackerFavicon=false save and restart qbt.

Note: You only need to edit the ini _if_ you upgraded from older qbt version. If you did a clean install then no editing is required.

This worked well for me. Thanks for it.

amaajemyfren on 7 May 2019

4.1.6 runs fine for me on win10-1809, but I noticed 2 silent crashes logged together (same time) after exiting the app. Only happened once so far. NEVER had a crash with 4.1.5 or previous versions for that matter.

Problem signature
Problem Event Name: APPCRASH
Application Name: qbittorrent.exe
Application Version: 4.1.6.0
Application Timestamp: 5ccf3300
Fault Module Name: qbittorrent.exe
Fault Module Version: 4.1.6.0
Fault Module Timestamp: 5ccf3300
Exception Code: c0000005
Exception Offset: 00000000008c3d60
OS Version: 10.0.17763.2.0.0.768.101
Locale ID: 1033
Additional Information 1: e84a
Additional Information 2: e84a7b18fff7d62ee31b8f374b0c7f8d
Additional Information 3: ac36
Additional Information 4: ac363ba8eb5209b61ecf6b3912806e3c

IntelliMoo on 7 May 2019

Same. 64-bit installer, Microsoft Windows v10.0.17763.475.

@Chocobo1, C:\Users\\AppData\Roaming... directory does not exist.

File qBittorrent.ini was not found on the computer.

Running as administrator does not fix the problem.

I have overwritten the original files with files from the qbittorrent_4.1.6_x64_for_issue_10581.7z archive. And run as administrator. Nothing has changed. qbittorrent_4.1.6_x64_for_issue_10581_v2.7z same.

@c0re100, qbittorrent_4.1.6_x64_openssl_1.0.7z works OK. Thanks!

Korb on 7 May 2019

@Korb does https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z work for you? It worked for me and v1/v2 did not.

LittleVulpix on 7 May 2019

@IntelliMoo this sucks if it crashes silently. This might lead on non-saved torrent progress at program exit.
Has anyone else seen the same?

I might need to redo everything with qt 5.12.3 and openssl 1.0.2r.

sledgehammer999 on 7 May 2019

@IntelliMoo this sucks if it crashes silently. This might lead on non-saved torrent progress at program exit.
Has anyone else seen the same?

I might need to redo everything with qt 5.12.3 and openssl 1.0.2r.

Yes, it would load, run minimized to the taskbar icon, then crash after 20-60 seconds. It doesn't give you any error messages, just closes. I have two pc's that run qBittorrent, and one works fine with 4.1.6, the other does not. Both are running windows 10 x64 pro, both are intel cpu, the pc that crashes has a Xeon 10 core cpu, the other a 6 core Intel I7. Both actually have the same motherboard chipset.

The only major differences are that the server that crashes, has the latest cumulative windows update installed, and it's seeding about 3800 torrents, it has 6 gb ram.

The pc that doesn't have any issues with 4.1.6 has about 200 torrents and 64 gb ram, and I haven't run that cumulative update on it yet.

Sleepovers on 7 May 2019

Well the same exact crash on exit happened again to mine: I was seeding 3 torrents overnight; just now I deleted them from the Transfers list, so then it was empty; a couple minutes later, I exited the app, and the same 2 crash entries appeared silently in the Windows reliability monitor. Then just to see what happens, I ran the app again, then simply exited it a minute later, and got 2 more of the exact same crash entries.

Hope this helps a bit. :)

IntelliMoo on 7 May 2019

I don't want to put a different issue in here, but even 4.1.5 sometimes crashed silently. It would usually happen after some time seeding, if I clicked on the icon to bring up the interface. It worked fine until then, but after clicking it just "disappeared". Probably a different issue, but thought I'd mention it. It wasn't frequent anyway.

LittleVulpix on 7 May 2019

4.1.6 runs fine for me on win10-1809, but I noticed 2 silent crashes logged together (same time) after exiting the app.

@IntelliMoo Wait a minute! Are you refering to the official release or the custom (v3) that I posted here?

@Sleepovers are you using the build that I posted here ?

sledgehammer999 on 7 May 2019

Official one. I can try the other soon.

Update -- Tried the v3 one, unfortunately same crash on exit (but new offset).

Exception Code: c0000005
Exception Offset: 00000000008c4e40

IntelliMoo on 8 May 2019

Starting from 4.1.6 (64-bit) version, every silent crash with Exception code: 0xc0000005 error. Tried to purge the installation and reinstall it can mitigate the issue. Today only one crash occurred, captured the crash dump and shows QHttpNetworkConnectionPrivate class (Qt related maybe?) failed.

FAULTING_IP: 
qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+9c
00007ff7`a80483e0 488b01          mov     rax,qword ptr [rcx]

Full dump output as below:

UMP_CLASS: 2

DUMP_QUALIFIER: 400

MODLIST_WITH_TSCHKSUM_HASH:  0e5098c6981528392511e14624d3bd8689d5c52b

MODLIST_SHA1_HASH:  520aa97b0179cac804c8b160ecfac01f8c0e77ba

NTGLOBALFLAG:  0

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

DUMP_FLAGS:  94

DUMP_TYPE:  1

CONTEXT:  (.ecxr)
rax=000001a5b1fb6ff8 rbx=000001a5a9f3aff0 rcx=0000000000000000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000000
rip=00007ff7a80483e0 rsp=0000009c1f7fc150 rbp=0000009c1f7fc300
 r8=0000000000000006  r9=000001a5a9dd7800 r10=000000000000001f
r11=000000000000005d r12=00000000000000e8 r13=0000000000000001
r14=0000000000000000 r15=000001a5ad3b7250
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00010202
qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+0x9c:
00007ff7`a80483e0 488b01          mov     rax,qword ptr [rcx] ds:00000000`00000000=????????????????
Resetting default scope

FAULTING_IP: 
qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+9c
00007ff7`a80483e0 488b01          mov     rax,qword ptr [rcx]

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ff7a80483e0 (qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+0x000000000000009c)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: 0000000000000000
Attempt to read from address 0000000000000000

DEFAULT_BUCKET_ID:  NULL_POINTER_READ

PROCESS_NAME:  qbittorrent.exe

FOLLOWUP_IP: 
qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+9c
00007ff7`a80483e0 488b01          mov     rax,qword ptr [rcx]

READ_ADDRESS:  0000000000000000 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000000

WATSON_BKT_PROCSTAMP:  5ccf3300

WATSON_BKT_PROCVER:  4.1.6.0

WATSON_BKT_MODULE:  qbittorrent.exe

WATSON_BKT_MODSTAMP:  5ccf3300

WATSON_BKT_MODOFFSET:  aa83e0

WATSON_BKT_MODVER:  4.1.6.0

BUILD_VERSION_STRING:  17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_HOST:  TU-DESKTOP

ANALYSIS_SESSION_TIME:  05-08-2019 15:32:57.0010

ANALYSIS_VERSION: 10.0.18869.1002 amd64fre

THREAD_ATTRIBUTES: 
OS_LOCALE:  ENU

BUGCHECK_STR:  APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ

PRIMARY_PROBLEM_CLASS:  APPLICATION_FAULT

PROBLEM_CLASSES: 

    ID:     [0n313]
    Type:   [@ACCESS_VIOLATION]
    Class:  Addendum
    Scope:  BUCKET_ID
    Name:   Omit
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x2f9c]
    Frame:  [0] : qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest

    ID:     [0n285]
    Type:   [INVALID_POINTER_READ]
    Class:  Primary
    Scope:  BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [Unspecified]
    TID:    [0x2f9c]
    Frame:  [0] : qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest

    ID:     [0n300]
    Type:   [NULL_POINTER_READ]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Add
    Data:   Omit
    PID:    [0x2c5c]
    TID:    [0x2f9c]
    Frame:  [0] : qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest

LAST_CONTROL_TRANSFER:  from 00007ff7a80494f9 to 00007ff7a80483e0

STACK_TEXT:  
0000009c`1f7fc150 00007ff7`a80494f9 : 000001a5`ae7af7c0 0000009c`1f7fc300 000001a5`ae7af7c0 00000000`0000005d : qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+0x9c
0000009c`1f7fc190 00007ff7`a80762ca : 00007ff7`a8ca43b8 000001a5`ad3b6950 000001a5`ae785e00 00000000`0000001f : qbittorrent!QHttpNetworkConnection::qt_static_metacall+0x79
0000009c`1f7fc1c0 00007ff7`a8076f2f : 000001a5`ad3b7250 00000000`00002f9c 0000009c`1f7fc250 00007ff7`a7fe7220 : qbittorrent!QMetaCallEvent::placeMetaCall+0x7a
0000009c`1f7fc200 00007ff7`a7bfd343 : 000001a5`a6976980 0000009c`1f7fc520 000001a5`ae7af7c0 000001a5`ad3b7250 : qbittorrent!QObject::event+0x12f
0000009c`1f7fc3f0 00007ff7`a7bfce50 : 00000000`00000000 0000009c`1f7fc520 00000000`00000002 00000000`00000000 : qbittorrent!QApplicationPrivate::notify_helper+0x10b
0000009c`1f7fc420 00007ff7`a7644990 : 000001a5`aff73d60 00007ffe`96fda765 000001a5`a9cf1e70 000001a5`a9c28980 : qbittorrent!QApplication::notify+0x1820
0000009c`1f7fc680 00007ff7`a80b1330 : 000001a5`a9c28980 000001a5`ad3b7250 00000000`00000400 000001a5`ad3b7250 : qbittorrent!Application::notify+0x20
0000009c`1f7fc6f0 00007ff7`a80b1eba : 0000009c`1f7fc8e9 00007ff7`a80e47a1 000001a5`a9c28980 00000000`00000000 : qbittorrent!QCoreApplication::notifyInternal2+0xc4
0000009c`1f7fc770 00007ff7`a819654d : 000001a5`a9c289b0 000001a5`00000000 00000000`00000000 0000009c`1f7fc820 : qbittorrent!QCoreApplicationPrivate::sendPostedEvents+0x22a
0000009c`1f7fc820 00007ffe`9925ca66 : 00000000`00000001 00000000`00000000 0000009c`1f7fca58 00000000`80000012 : qbittorrent!qt_internal_proc+0x3cd
0000009c`1f7fc950 00007ffe`9925c582 : 000001a5`a705e8f0 00007ff7`a8196180 00000000`000906d0 0000009c`1f7fcb80 : user32!UserCallWinProcCheckWow+0x266
0000009c`1f7fcad0 00007ff7`a8197716 : 0000009c`1f7fcb80 00000000`00000000 00000000`00000024 000001a5`a9cb0840 : user32!DispatchMessageWorker+0x1b2
0000009c`1f7fcb50 00007ff7`a819ae57 : 000001a5`a9c89701 00000000`00000000 000001a5`a9c28900 000001a5`00000000 : qbittorrent!QEventDispatcherWin32::processEvents+0x476
0000009c`1f7ffd40 00007ff7`a80f94f6 : 0000009c`00000004 000001a5`a9cd2810 000001a5`00000024 000001a5`00000004 : qbittorrent!QEventLoop::exec+0x22f
0000009c`1f7ffde0 00007ff7`a80e4ead : 000001a5`a9cd2810 000001a5`a9cd2810 000001a5`a9cba9c8 000001a5`a9cba9c0 : qbittorrent!QThread::run+0x96
0000009c`1f7ffe30 00007ff7`a825b2dd : 000001a5`a9cc22c0 000001a5`a9cba9c0 00000000`00000000 00000000`00000000 : qbittorrent!QThreadPrivate::start+0xdd
0000009c`1f7ffe70 00007ffe`989c7974 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : qbittorrent!thread_start<unsigned int (__cdecl*)(void * __ptr64)>+0x5d
0000009c`1f7ffea0 00007ffe`9b6da271 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0x14
0000009c`1f7ffed0 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x21


THREAD_SHA1_HASH_MOD_FUNC:  c8459758d78ce10dd4d31100e434d57864aaf8b9

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  6ec8f57e1e2e989a3bcf520da5e74dd24fc64602

THREAD_SHA1_HASH_MOD:  76f7b4851594718068cb92bfd09f48de8c98e0ff

FAULT_INSTR_CODE:  ff018b48

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+9c

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: qbittorrent

IMAGE_NAME:  qbittorrent.exe

DEBUG_FLR_IMAGE_TIMESTAMP:  5ccf3300

STACK_COMMAND:  ~15s ; .ecxr ; kb

FAILURE_BUCKET_ID:  NULL_POINTER_READ_c0000005_qbittorrent.exe!QHttpNetworkConnectionPrivate::_q_startNextRequest

BUCKET_ID:  APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ_qbittorrent!QHttpNetworkConnectionPrivate::_q_startNextRequest+9c

FAILURE_EXCEPTION_CODE:  c0000005

FAILURE_IMAGE_NAME:  qbittorrent.exe

BUCKET_ID_IMAGE_STR:  qbittorrent.exe

FAILURE_MODULE_NAME:  qbittorrent

BUCKET_ID_MODULE_STR:  qbittorrent

FAILURE_FUNCTION_NAME:  QHttpNetworkConnectionPrivate::_q_startNextRequest

BUCKET_ID_FUNCTION_STR:  QHttpNetworkConnectionPrivate::_q_startNextRequest

BUCKET_ID_OFFSET:  9c

BUCKET_ID_MODTIMEDATESTAMP:  5ccf3300

BUCKET_ID_MODCHECKSUM:  0

BUCKET_ID_MODVER_STR:  4.1.6.0

BUCKET_ID_PREFIX_STR:  APPLICATION_FAULT_NULL_POINTER_READ_INVALID_POINTER_READ_

FAILURE_PROBLEM_CLASS:  APPLICATION_FAULT

FAILURE_SYMBOL_NAME:  qbittorrent.exe!QHttpNetworkConnectionPrivate::_q_startNextRequest

TARGET_TIME:  2019-05-08T05:31:53.000Z

OSBUILD:  17763

OSSERVICEPACK:  475

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

SUITE_MASK:  256

PRODUCT_TYPE:  1

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  1989-09-10 14:58:46

BUILDDATESTAMP_STR:  180914-1434

BUILDLAB_STR:  rs5_release

BUILDOSVER_STR:  10.0.17763.1.amd64fre.rs5_release.180914-1434

ANALYSIS_SESSION_ELAPSED_TIME:  a61

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:null_pointer_read_c0000005_qbittorrent.exe!qhttpnetworkconnectionprivate::_q_startnextrequest

FAILURE_ID_HASH:  {ac274603-3ec7-4eba-9c02-9fdf6ae7e9a5}

Followup:     MachineOwner
---------

JoshDaone on 8 May 2019

@Sleepovers are you using the build that I posted here ?

Yes, I tested it too. I am using the original 4.1.6 release on the pc it works on, and I have reverted back to 4.1.5 on the server that all 4 builds of 4.1.6 crashes on.

Sleepovers on 8 May 2019

@JoshDaone is your dump from the official 4.1.6 release of from custom build?
If it is from the official, can you capture a crash dump from the custom build too?
Link to custom: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z

@ all
This is a longshot: Does any of you have WinDbg installed?

sledgehammer999 on 8 May 2019

Reproduced on official build 4.1.6 x64 on Win10 x64 1809. Administrator execution is a work around.

shnorb on 8 May 2019

Official build crashed for me, but either this custom build or setting DownloadTrackerFavicon to false fixed it. Not running as admin.

Razunter on 8 May 2019

@sledgehammer999
win 10 x64 pro 1903 (18362.86)
32gb ram
4.1.6 (v3)

Faulting application name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5cd0ba58
Faulting module name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5cd0ba58
Exception code: 0xc0000005
Fault offset: 0x00000000008c4e40
Faulting process ID: 0xa1c
Faulting application start time: 0x01d504bb4bfeb4f8
Faulting application path: C:\Program Files\qBittorrent\qbittorrent.exe
Faulting module path: C:\Program Files\qBittorrent\qbittorrent.exe
Report ID: d652f634-5614-48b9-96bb-a08324b400cc
Faulting package full name:
Faulting package-relative application ID:

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

Problem signature:
P1: qbittorrent.exe
P2: 4.1.6.0
P3: 5cd0ba58
P4: qbittorrent.exe
P5: 4.1.6.0
P6: 5cd0ba58
P7: c0000005
P8: 00000000008c4e40
P9:
P10:

Faulting application name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5cd0ba58
Faulting module name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5cd0ba58
Exception code: 0xc0000005
Fault offset: 0x00000000008c4e40
Faulting process ID: 0xa1c
Faulting application start time: 0x01d504bb4bfeb4f8
Faulting application path: C:\Program Files\qBittorrent\qbittorrent.exe
Faulting module path: C:\Program Files\qBittorrent\qbittorrent.exe
Report ID: e8a6549b-9597-4dac-be06-8953ac947b75
Faulting package full name:
Faulting package-relative application ID:

installing windbg preview from here (for debugging help/will need guidance!):
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/debugger-download-tools

xavier2k6 on 8 May 2019

@sledgehammer999

(hope this is what you need)

CommandLine: "C:\Program Files\qBittorrent\qbittorrent.exe"
Symbol search path is: srv*
Executable search path is:
ModLoad: 00007ff745a70000 00007ff747253000 qbittorrent.exe
ModLoad: 00007ffea27a0000 00007ffea2990000 ntdll.dll
ModLoad: 00007ffea2630000 00007ffea26e2000 C:\WINDOWS\System32\KERNEL32.DLL
ModLoad: 00007ffea0140000 00007ffea03e2000 C:\WINDOWS\System32\KERNELBASE.dll
ModLoad: 00007ffea1850000 00007ffea1f30000 C:\WINDOWS\System32\SHELL32.dll
ModLoad: 00007ffea0610000 00007ffea070a000 C:\WINDOWS\System32\ucrtbase.dll
ModLoad: 00007ffe9f730000 00007ffe9f77a000 C:\WINDOWS\System32\cfgmgr32.dll
ModLoad: 00007ffea1420000 00007ffea14c9000 C:\WINDOWS\System32\shcore.dll
ModLoad: 00007ffea1000000 00007ffea109e000 C:\WINDOWS\System32\msvcrt.dll
ModLoad: 00007ffea20a0000 00007ffea21c0000 C:\WINDOWS\System32\RPCRT4.dll
ModLoad: 00007ffea10d0000 00007ffea1406000 C:\WINDOWS\System32\combase.dll
ModLoad: 00007ffea00b0000 00007ffea0131000 C:\WINDOWS\System32\bcryptPrimitives.dll
ModLoad: 00007ffe9f900000 00007ffea007b000 C:\WINDOWS\System32\windows.storage.dll
ModLoad: 00007ffe9f830000 00007ffe9f8ce000 C:\WINDOWS\System32\msvcp_win.dll
ModLoad: 00007ffea21c0000 00007ffea2257000 C:\WINDOWS\System32\sechost.dll
ModLoad: 00007ffea2580000 00007ffea2623000 C:\WINDOWS\System32\advapi32.dll
ModLoad: 00007ffe9f710000 00007ffe9f72f000 C:\WINDOWS\System32\profapi.dll
ModLoad: 00007ffe9f6a0000 00007ffe9f6ea000 C:\WINDOWS\System32\powrprof.dll
ModLoad: 00007ffe9f670000 00007ffe9f680000 C:\WINDOWS\System32\UMPDC.dll
ModLoad: 00007ffea2700000 00007ffea2752000 C:\WINDOWS\System32\shlwapi.dll
ModLoad: 00007ffea0a10000 00007ffea0a36000 C:\WINDOWS\System32\GDI32.dll
ModLoad: 00007ffe9f8d0000 00007ffe9f8f1000 C:\WINDOWS\System32\win32u.dll
ModLoad: 00007ffea03f0000 00007ffea0584000 C:\WINDOWS\System32\gdi32full.dll
ModLoad: 00007ffea1640000 00007ffea17d3000 C:\WINDOWS\System32\USER32.dll
ModLoad: 00007ffe9f680000 00007ffe9f691000 C:\WINDOWS\System32\kernel.appcore.dll
ModLoad: 00007ffea0590000 00007ffea05a7000 C:\WINDOWS\System32\cryptsp.dll
ModLoad: 00007ffea10a0000 00007ffea10ce000 C:\WINDOWS\System32\IMM32.dll
ModLoad: 00007ffe9afa0000 00007ffe9b194000 C:\WINDOWS\SYSTEM32\dbghelp.dll
ModLoad: 00007ffea0a40000 00007ffea0b04000 C:\WINDOWS\System32\OLEAUT32.dll
ModLoad: 00007ffea14e0000 00007ffea1636000 C:\WINDOWS\System32\ole32.dll
ModLoad: 00007ffe9da40000 00007ffe9dad9000 C:\WINDOWS\SYSTEM32\UxTheme.dll
ModLoad: 00007ffe9bde0000 00007ffe9bdf3000 C:\WINDOWS\SYSTEM32\WTSAPI32.dll
ModLoad: 00007ffe9de60000 00007ffe9de8d000 C:\WINDOWS\SYSTEM32\dwmapi.dll
ModLoad: 00007ffea17e0000 00007ffea184f000 C:\WINDOWS\System32\WS2_32.dll
ModLoad: 00007ffe9ebe0000 00007ffe9ec1a000 C:\WINDOWS\SYSTEM32\IPHLPAPI.DLL
ModLoad: 00007ffea0080000 00007ffea00a6000 C:\WINDOWS\System32\bcrypt.dll
ModLoad: 00007ffe8a350000 00007ffe8a36b000 C:\WINDOWS\SYSTEM32\MPR.dll
ModLoad: 00007ffea0710000 00007ffea0859000 C:\WINDOWS\System32\CRYPT32.dll
ModLoad: 00007ffe9f560000 00007ffe9f585000 C:\WINDOWS\SYSTEM32\USERENV.dll
ModLoad: 00007ffe8eb90000 00007ffe8eba7000 C:\WINDOWS\SYSTEM32\NETAPI32.dll
ModLoad: 00007ffe9f6f0000 00007ffe9f702000 C:\WINDOWS\System32\MSASN1.dll
ModLoad: 00007ffe99150000 00007ffe9915a000 C:\WINDOWS\SYSTEM32\VERSION.dll
ModLoad: 00007ffe9ee80000 00007ffe9eee7000 C:\WINDOWS\SYSTEM32\MSWSOCK.dll
ModLoad: 00007ffe97d10000 00007ffe97d34000 C:\WINDOWS\SYSTEM32\WINMM.dll
ModLoad: 00007ffe97ad0000 00007ffe97afd000 C:\WINDOWS\SYSTEM32\winmmbase.dll
ModLoad: 0000020c8ad50000 0000020c8ad7d000 C:\WINDOWS\SYSTEM32\WINMMBASE.dll
ModLoad: 0000020c8ad80000 0000020c8adad000 C:\WINDOWS\SYSTEM32\winmmbase.dll
ModLoad: 00007ffe9f050000 00007ffe9f05c000 C:\WINDOWS\SYSTEM32\CRYPTBASE.DLL
ModLoad: 00007ffe9ecf0000 00007ffe9ecfc000 C:\WINDOWS\SYSTEM32\NETUTILS.DLL
ModLoad: 00007ffe8f0c0000 00007ffe8f0e6000 C:\WINDOWS\SYSTEM32\SRVCLI.DLL
(24f0.1a8c): Break instruction exception - code 80000003 (first chance)
ntdll!LdrpDoDebuggerBreak+0x30:
00007ffe`a28711dc cc int 3

xavier2k6 on 8 May 2019

@xavier2k6 almost! In the "command subwindow" AND after the crash input this: |* !analyze -v -f
A bit more instructions based on older WinDbg: https://github.com/qbittorrent/qBittorrent/issues/5785#issuecomment-250839116

sledgehammer999 on 8 May 2019

Can confirm silent crashes which are fixed by this build:

This build is v4.1.6 but uses the newer Qt 5.12.3.
link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z

NOTE: All my test builds( and original 4.1.6) use openssl 1.1.1b. While the original 4.1.5 build used the 1.0.x series. That's the next thing I am going to change if this build doesn't work.

pozemka on 8 May 2019

0:000> |* ~* kp

.  0  Id: 26b0.2cb4 Suspend: 1 Teb: 000000f7`c5f6b000 Unfrozen
 # Child-SP          RetAddr           Call Site
00 000000f7`c67ff0b0 00007ffe`a287459f ntdll!LdrpDoDebuggerBreak+0x30
01 000000f7`c67ff0f0 00007ffe`a2861dbd ntdll!LdrpInitializeProcess+0x1e57
02 000000f7`c67ff530 00007ffe`a28117f3 ntdll!_LdrpInitialize+0x505b1
03 000000f7`c67ff5d0 00007ffe`a281179e ntdll!LdrpInitialize+0x3b
04 000000f7`c67ff600 00000000`00000000 ntdll!LdrInitializeThunk+0xe

   1  Id: 26b0.a04 Suspend: 1 Teb: 000000f7`c5f6d000 Unfrozen
 # Child-SP          RetAddr           Call Site
00 000000f7`c6fff778 00007ffe`a27d3ff0 ntdll!NtWaitForWorkViaWorkerFactory+0x14
01 000000f7`c6fff780 00007ffe`a2647bd4 ntdll!TppWorkerThread+0x300
02 000000f7`c6fffb40 00007ffe`a280ce71 KERNEL32!BaseThreadInitThunk+0x14
03 000000f7`c6fffb70 00000000`00000000 ntdll!RtlUserThreadStart+0x21

   2  Id: 26b0.4c0 Suspend: 1 Teb: 000000f7`c5f6f000 Unfrozen
 # Child-SP          RetAddr           Call Site
00 000000f7`c77ff778 00007ffe`a27d3ff0 ntdll!NtWaitForWorkViaWorkerFactory+0x14
01 000000f7`c77ff780 00007ffe`a2647bd4 ntdll!TppWorkerThread+0x300
02 000000f7`c77ffb40 00007ffe`a280ce71 KERNEL32!BaseThreadInitThunk+0x14
03 000000f7`c77ffb70 00000000`00000000 ntdll!RtlUserThreadStart+0x21

   3  Id: 26b0.ad8 Suspend: 1 Teb: 000000f7`c5f71000 Unfrozen
 # Child-SP          RetAddr           Call Site
00 000000f7`c7fffa28 00007ffe`a27d3ff0 ntdll!NtWaitForWorkViaWorkerFactory+0x14
01 000000f7`c7fffa30 00007ffe`a2647bd4 ntdll!TppWorkerThread+0x300
02 000000f7`c7fffdf0 00007ffe`a280ce71 KERNEL32!BaseThreadInitThunk+0x14
03 000000f7`c7fffe20 00000000`00000000 ntdll!RtlUserThreadStart+0x21
0:000> |* !analyze -v -f
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

*** WARNING: Unable to verify checksum for qbittorrent.exe

KEY_VALUES_STRING: 1

    Key  : Timeline.OS.Boot.DeltaSec
    Value: 474180

    Key  : Timeline.Process.Start.DeltaSec
    Value: 38


PROCESSES_ANALYSIS: 1

SERVICE_ANALYSIS: 1

STACKHASH_ANALYSIS: 1

TIMELINE_ANALYSIS: 1

Timeline: !analyze.Start
    Name: <blank>
    Time: 2019-05-08T11:39:06.194Z
    Diff: 194 mSec

Timeline: Dump.Current
    Name: <blank>
    Time: 2019-05-08T11:39:06.0Z
    Diff: 0 mSec

Timeline: Process.Start
    Name: <blank>
    Time: 2019-05-08T11:38:28.0Z
    Diff: 38000 mSec

Timeline: OS.Boot
    Name: <blank>
    Time: 2019-05-02T23:56:06.0Z
    Diff: 474180000 mSec


DUMP_CLASS: 2

DUMP_QUALIFIER: 0

FAULTING_IP: 
ntdll!LdrpDoDebuggerBreak+30
00007ffe`a28711dc cc              int     3

EXCEPTION_RECORD:  (.exr -1)
ExceptionAddress: 00007ffea28711dc (ntdll!LdrpDoDebuggerBreak+0x0000000000000030)
   ExceptionCode: 80000003 (Break instruction exception)
  ExceptionFlags: 00000000
NumberParameters: 1
   Parameter[0]: 0000000000000000

FAULTING_THREAD:  00002cb4

BUGCHECK_STR:  BREAKPOINT

DEFAULT_BUCKET_ID:  BREAKPOINT

PROCESS_NAME:  qbittorrent.exe

ERROR_CODE: (NTSTATUS) 0x80000003 - {EXCEPTION}  Breakpoint  A breakpoint has been reached.

EXCEPTION_CODE: (HRESULT) 0x80000003 (2147483651) - One or more arguments are invalid

EXCEPTION_CODE_STR:  80000003

EXCEPTION_PARAMETER1:  0000000000000000

WATSON_BKT_PROCSTAMP:  5cd0ba58

WATSON_BKT_PROCVER:  4.1.6.0

WATSON_BKT_MODULE:  ntdll.dll

WATSON_BKT_MODSTAMP:  a52b7c6a

WATSON_BKT_MODOFFSET:  d11dc

WATSON_BKT_MODVER:  10.0.18362.1

MODULE_VER_PRODUCT:  Microsoft® Windows® Operating System

BUILD_VERSION_STRING:  18362.1.amd64fre.19h1_release.190318-1202

MODLIST_WITH_TSCHKSUM_HASH:  b170c78f0e1c921a7e42b44ce8b52f4508d2de2c

MODLIST_SHA1_HASH:  eeccd84d549a961d1735c7070dc79bf496bbf025

NTGLOBALFLAG:  70

PROCESS_BAM_CURRENT_THROTTLED: 0

PROCESS_BAM_PREVIOUS_THROTTLED: 0

APPLICATION_VERIFIER_FLAGS:  0

PRODUCT_TYPE:  1

SUITE_MASK:  272

DUMP_TYPE:  fe

ANALYSIS_SESSION_HOST:  DESKTOP-45Q189V

ANALYSIS_SESSION_TIME:  05-08-2019 12:39:06.0194

ANALYSIS_VERSION: 10.0.18362.1 amd64fre

THREAD_ATTRIBUTES: 
OS_LOCALE:  ENG

PRIMARY_PROBLEM_CLASS:  BREAKPOINT

PROBLEM_CLASSES: 

    ID:     [0n321]
    Type:   [@APPLICATION_FAULT_STRING]
    Class:  Primary
    Scope:  DEFAULT_BUCKET_ID (Failure Bucket ID prefix)
            BUCKET_ID
    Name:   Omit
    Data:   Add
            String: [BREAKPOINT]
    PID:    [Unspecified]
    TID:    [Unspecified]
    Frame:  [0]

LAST_CONTROL_TRANSFER:  from 00007ffea287459f to 00007ffea28711dc

STACK_TEXT:  
000000f7`c67ff0b0 00007ffe`a287459f : 000000f7`c5f6a000 00007ffe`a28cd4b0 00007ffe`a28cd4b0 00007ffe`a28cd4b0 : ntdll!LdrpDoDebuggerBreak+0x30
000000f7`c67ff0f0 00007ffe`a2861dbd : 00000000`00000001 00000000`00000000 00000000`00000000 00000000`00000001 : ntdll!LdrpInitializeProcess+0x1e57
000000f7`c67ff530 00007ffe`a28117f3 : 00000000`00000000 00007ffe`a27a0000 00000000`00000000 000000f7`c5f6b000 : ntdll!_LdrpInitialize+0x505b1
000000f7`c67ff5d0 00007ffe`a281179e : 000000f7`c67ff650 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrpInitialize+0x3b
000000f7`c67ff600 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!LdrInitializeThunk+0xe


THREAD_SHA1_HASH_MOD_FUNC:  f6d506c4546bb5d137f475a99d6cb238658f395a

THREAD_SHA1_HASH_MOD_FUNC_OFFSET:  cbe37069a2849d5f061d49f8b0ad8d35cabfb661

THREAD_SHA1_HASH_MOD:  421247e39d7ac2afa4b65a67c08f22894942361d

FOLLOWUP_IP: 
ntdll!LdrpDoDebuggerBreak+30
00007ffe`a28711dc cc              int     3

FAULT_INSTR_CODE:  4800ebcc

SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  ntdll!LdrpDoDebuggerBreak+30

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: ntdll

IMAGE_NAME:  ntdll.dll

DEBUG_FLR_IMAGE_TIMESTAMP:  0

STACK_COMMAND:  dt ntdll!LdrpLastDllInitializer BaseDllName ; dt ntdll!LdrpFailureData ; ~0s ; .cxr ; kb

BUCKET_ID:  BREAKPOINT_ntdll!LdrpDoDebuggerBreak+30

FAILURE_EXCEPTION_CODE:  80000003

FAILURE_IMAGE_NAME:  ntdll.dll

BUCKET_ID_IMAGE_STR:  ntdll.dll

FAILURE_MODULE_NAME:  ntdll

BUCKET_ID_MODULE_STR:  ntdll

FAILURE_FUNCTION_NAME:  LdrpDoDebuggerBreak

BUCKET_ID_FUNCTION_STR:  LdrpDoDebuggerBreak

BUCKET_ID_OFFSET:  30

BUCKET_ID_MODTIMEDATESTAMP:  0

BUCKET_ID_MODCHECKSUM:  1f6968

BUCKET_ID_MODVER_STR:  10.0.18362.1

BUCKET_ID_PREFIX_STR:  BREAKPOINT_

FAILURE_PROBLEM_CLASS:  BREAKPOINT

FAILURE_SYMBOL_NAME:  ntdll.dll!LdrpDoDebuggerBreak

FAILURE_BUCKET_ID:  BREAKPOINT_80000003_ntdll.dll!LdrpDoDebuggerBreak

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/qbittorrent.exe/4.1.6.0/5cd0ba58/ntdll.dll/10.0.18362.1/a52b7c6a/80000003/000d11dc.htm?Retriage=1

TARGET_TIME:  2019-05-08T11:39:57.000Z

OSBUILD:  18362

OSSERVICEPACK:  86

SERVICEPACK_NUMBER: 0

OS_REVISION: 0

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

OSEDITION:  Windows 10 WinNt SingleUserTS

USER_LCID:  0

OSBUILD_TIMESTAMP:  unknown_date

BUILDDATESTAMP_STR:  190318-1202

BUILDLAB_STR:  19h1_release

BUILDOSVER_STR:  10.0.18362.1.amd64fre.19h1_release.190318-1202

ANALYSIS_SESSION_ELAPSED_TIME:  10f98

ANALYSIS_SOURCE:  UM

FAILURE_ID_HASH_STRING:  um:breakpoint_80000003_ntdll.dll!ldrpdodebuggerbreak

FAILURE_ID_HASH:  {06f54d4d-201f-7f5c-0224-0b1f2e1e15a5}

Followup:     MachineOwner
---------

0:000> |* lm
start             end                 module name
00007ff7`45a70000 00007ff7`47253000   qbittorrent C (private pdb symbols)  C:\Program Files\qBittorrent\qbittorrent.pdb
00007ffe`8a350000 00007ffe`8a36b000   MPR        (deferred)             
00007ffe`8eb90000 00007ffe`8eba7000   NETAPI32   (deferred)             
00007ffe`8f0c0000 00007ffe`8f0e6000   SRVCLI     (deferred)             
00007ffe`97ad0000 00007ffe`97afd000   WINMMBASE   (deferred)             
00007ffe`97d10000 00007ffe`97d34000   WINMM      (pdb symbols)          c:\mss\winmm.pdb\6D145E3B6417F20C489BD311F39E921B1\winmm.pdb
00007ffe`99150000 00007ffe`9915a000   VERSION    (deferred)             
00007ffe`9afa0000 00007ffe`9b194000   dbghelp    (deferred)             
00007ffe`9bde0000 00007ffe`9bdf3000   WTSAPI32   (deferred)             
00007ffe`9da40000 00007ffe`9dad9000   UxTheme    (deferred)             
00007ffe`9de60000 00007ffe`9de8d000   dwmapi     (deferred)             
00007ffe`9ebe0000 00007ffe`9ec1a000   IPHLPAPI   (deferred)             
00007ffe`9ecf0000 00007ffe`9ecfc000   NETUTILS   (deferred)             
00007ffe`9ee80000 00007ffe`9eee7000   MSWSOCK    (deferred)             
00007ffe`9f050000 00007ffe`9f05c000   CRYPTBASE   (deferred)             
00007ffe`9f560000 00007ffe`9f585000   USERENV    (deferred)             
00007ffe`9f670000 00007ffe`9f680000   UMPDC      (deferred)             
00007ffe`9f680000 00007ffe`9f691000   kernel_appcore   (deferred)             
00007ffe`9f6a0000 00007ffe`9f6ea000   powrprof   (deferred)             
00007ffe`9f6f0000 00007ffe`9f702000   MSASN1     (deferred)             
00007ffe`9f710000 00007ffe`9f72f000   profapi    (deferred)             
00007ffe`9f730000 00007ffe`9f77a000   cfgmgr32   (deferred)             
00007ffe`9f830000 00007ffe`9f8ce000   msvcp_win   (deferred)             
00007ffe`9f8d0000 00007ffe`9f8f1000   win32u     (deferred)             
00007ffe`9f900000 00007ffe`a007b000   windows_storage   (deferred)             
00007ffe`a0080000 00007ffe`a00a6000   bcrypt     (deferred)             
00007ffe`a00b0000 00007ffe`a0131000   bcryptPrimitives   (deferred)             
00007ffe`a0140000 00007ffe`a03e2000   KERNELBASE   (pdb symbols)          c:\mss\kernelbase.pdb\1C82CBDD70F5F0099D85850486D5613F1\kernelbase.pdb
00007ffe`a03f0000 00007ffe`a0584000   gdi32full   (deferred)             
00007ffe`a0590000 00007ffe`a05a7000   cryptsp    (deferred)             
00007ffe`a0610000 00007ffe`a070a000   ucrtbase   (deferred)             
00007ffe`a0710000 00007ffe`a0859000   CRYPT32    (deferred)             
00007ffe`a0a10000 00007ffe`a0a36000   GDI32      (deferred)             
00007ffe`a0a40000 00007ffe`a0b04000   OLEAUT32   (deferred)             
00007ffe`a1000000 00007ffe`a109e000   msvcrt     (deferred)             
00007ffe`a10a0000 00007ffe`a10ce000   IMM32      (deferred)             
00007ffe`a10d0000 00007ffe`a1406000   combase    (deferred)             
00007ffe`a1420000 00007ffe`a14c9000   shcore     (deferred)             
00007ffe`a14e0000 00007ffe`a1636000   ole32      (private pdb symbols)  c:\mss\ole32.pdb\EC385CEE495BF16259FEC3724F96A5831\ole32.pdb
00007ffe`a1640000 00007ffe`a17d3000   USER32     (pdb symbols)          c:\mss\user32.pdb\BC4CC7CC9A33B8A66AEA91BFB0D5FCAA1\user32.pdb
00007ffe`a17e0000 00007ffe`a184f000   WS2_32     (deferred)             
00007ffe`a1850000 00007ffe`a1f30000   SHELL32    (deferred)             
00007ffe`a20a0000 00007ffe`a21c0000   RPCRT4     (deferred)             
00007ffe`a21c0000 00007ffe`a2257000   sechost    (deferred)             
00007ffe`a2580000 00007ffe`a2623000   advapi32   (deferred)             
00007ffe`a2630000 00007ffe`a26e2000   KERNEL32   (pdb symbols)          c:\mss\kernel32.pdb\B6F0E183C96D92A697EFA1F4B153B8151\kernel32.pdb
00007ffe`a2700000 00007ffe`a2752000   shlwapi    (deferred)             
00007ffe`a27a0000 00007ffe`a2990000   ntdll      (pdb symbols)          c:\mss\ntdll.pdb\B54F3499813EBCF139AEFDD664E98FDD1\ntdll.pdb

xavier2k6 on 8 May 2019

@xavier2k6 did you have the qbittorrent.pdb file alongside qbittorrent.exe too? If not, please try again.

sledgehammer999 on 8 May 2019

@xavier2k6 did you have the qbittorrent.pdb file alongside qbittorrent.exe too? If not, please try again.

Nevermind, it seems you have it.

The stacktrace unfortunately doesn't show something from qbittorrent/qt. It shows Windows functions...

sledgehammer999 on 8 May 2019

@sledgehammer999
Just confirming that I did/do have the qbittorrent.pdb file alongside qbittorrent.exe too.
Anything else you would like me to try?!

xavier2k6 on 8 May 2019

@sledgehammer999
I may be wrong but I don't think QT fully supports OpenSSL 1.1.x yet

'Agreement to update openSSL 1.1* before Qt 5.13.0 official release'
https://lists.qt-project.org/pipermail/releasing/2019-March/002614.html

We should start using OpenSSL 1.1.1 (LTS) instead of 1.0.2x(LTS) version as 1.0.2 support will end 31.12.2019
https://bugreports.qt.io/browse/QTQAINFRA-2327?jql=text%20~%20%22openssl%201.1.1%22

Would you like me to test/stacktrace a custom 4.1.6 QT 5.12.3/OpenSSL 1.0.2r build if you can provide it?

xavier2k6 on 8 May 2019

I managed to capture the call stack from the Visual Studio Debugger:

qbittorrent.exe!QHttpNetworkConnectionPrivate::_q_startNextRequest(void)
qbittorrent.exe!QHttpNetworkConnection::qt_static_metacall(class QObject *,enum QMetaObject::Call,int,void * *)
qbittorrent.exe!QMetaCallEvent::placeMetaCall(class QObject *)
qbittorrent.exe!QObject::event(class QEvent *)
qbittorrent.exe!QApplicationPrivate::notify_helper(class QObject *,class QEvent *)
qbittorrent.exe!QApplication::notify(class QObject *,class QEvent *)
qbittorrent.exe!Application::notify(QObject * receiver, QEvent * event) Line 626
    at g:\qbittorrent\qbittorrent-4.1.6\src\app\application.cpp(626)
[External Code]
[Inline Frame] qbittorrent.exe!invoke_thread_procedure(unsigned int(*)(void *) context, void * const) Line 91
    at d:\th\minkernel\crts\ucrt\src\appcrt\startup\thread.cpp(91)
qbittorrent.exe!thread_start<unsigned int (__cdecl*)(void * __ptr64)>(void * const parameter) Line 115
    at d:\th\minkernel\crts\ucrt\src\appcrt\startup\thread.cpp(115)
[External Code]

DominikDeak on 8 May 2019

@xavier2k6
I may be wrong but I don't think QT fully supports OpenSSL 1.1.x yet

'Agreement to update openSSL 1.1* before Qt 5.13.0 official release'
https://lists.qt-project.org/pipermail/releasing/2019-March/002614.html

We should start using OpenSSL 1.1.1 (LTS) instead of 1.0.2x(LTS) version as 1.0.2 support will end 31.12.2019
https://bugreports.qt.io/browse/QTQAINFRA-2327?jql=text%20~%20%22openssl%201.1.1%22

Would you like me to test/stacktrace a custom 4.1.6 QT 5.12.3/OpenSSL 1.0.2r build if you can provide it?

Good point, quick check on the first link and seems they are shipping openSSL 1.1* in 5.12.x and 5.13.0

@sledgehammer999 The memory dump was captured from official 4.1.6, haven't try the new qbittorrent_4.1.6_x64_for_issue_10581_v3.7z build yet, I will have the dump for you if crash again.

JoshDaone on 8 May 2019

I've read most of this thread (skim style) and I didn't see it mentioned yet that:

The silent crash only seems to occur during inactive (i.e. no actual uploading) seeding. If there is an actively downloading torrent, then the program does it's thing as normal until the download completes.

Hope this helps narrow down the issue, thanks for continuing to solve the problem everyone.

Win 10 Enterprise x64 1809

CptBlinky on 8 May 2019

In my case I can just start the app (empty), wait a minute, then exit the
app, and I get 2 identical silent crashes logged.

The silent crash only seems to occur during inactive (i.e. no actual
uploading) seeding. If there is an actively downloading torrent, then the
program does it's thing ...

IntelliMoo on 8 May 2019

In my case I can just start the app (empty), wait a minute, then exit the app, and I get 2 identical silent crashes logged.
…
The silent crash only seems to occur during inactive (i.e. no actual uploading) seeding. If there is an actively downloading torrent, then the program does it's thing ...

Indeed. So it seems the crash only occurs when the app is 'idle', but if there is actually traffic, then it runs normally...

Btw, where are the crashes logged?

CptBlinky on 8 May 2019

I suspect it is the same as #9667 (comment)
So you'll need to edit C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini and change DownloadTrackerFavicon=true to DownloadTrackerFavicon=false save and restart qbt.

Note: You only need to edit the ini _if_ you upgraded from older qbt version. If you did a clean install then no editing is required.

Thank you! It worked for me!

teslasystems on 8 May 2019

>

Btw, where are the crashes logged?

Control Panel - Security and Maintenance - Reliability Monitor, and Event
Viewer - Application.

IntelliMoo on 8 May 2019

👍1

I suspect it is the same as #9667 (comment)
So you'll need to edit C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini and change DownloadTrackerFavicon=true to DownloadTrackerFavicon=false save and restart qbt.
Note: You only need to edit the ini _if_ you upgraded from older qbt version. If you did a clean install then no editing is required.

This worked well for me. Thanks for it.

After a few days of issues with this I would like to rescind this. I have had to revert to v4.1.5.

amaajemyfren on 10 May 2019

Personally, I'm using @sledgehammer999 's "v3" version from here:

https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z

with no issues. None of the other solutions worked for me.

LittleVulpix on 10 May 2019

After a few days of issues with this I would like to rescind this. I have had to revert to v4.1.5.

Did you even try build v3 as LittleVulpix quoted above me?

Ryrynz on 10 May 2019

After a few days of issues with this I would like to rescind this. I have had to revert to v4.1.5.

Did you even try build v3 as LittleVulpix quoted above me?

No I did not - I had only used the config changes given. Was updating it in case someone was tracking how many issues were resolved by changing the config.

amaajemyfren on 10 May 2019

Went back to 4.1.5 as well, exiting the app was destroying the Reliability Monitor rating. lol

IntelliMoo on 10 May 2019

Personally, I'm using @sledgehammer999 's "v3" version from here:

https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v3.7z

with no issues. None of the other solutions worked for me.

This build also works for me since last time crash.

JoshDaone on 11 May 2019

Very weird indeed, I just installed the standard version of QBT 4.1.6 and it just worked....

Sleepovers on 12 May 2019

@IntelliMoo can you try the following build? v4.1.6, Qt5 5.12.3, openssl 1.0.2r
Link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v4.7z

sledgehammer999 on 12 May 2019

❤2

Will try v4...

Update: Success! v4 does not crash on exit.

IntelliMoo on 12 May 2019

Hope this helps: Visual studio 2017 attached to process
Seems networking-related in my case

zeilja on 13 May 2019

@zeilja which version did you use? The official 4.1.6 or one of my custom builds from this thread?

sledgehammer999 on 13 May 2019

the official one. I am trying to compile on windows but so far unsuccessful with visual studio or qt creator. Need to compile deps first.

I'm on win 8.1 pro x64

zeilja on 13 May 2019

@zeilja We know about the official one. We don't want more debugging.
The v3 custom build of mine, works fine, but some users have reported that it crashes during exit. It would be nice if you could catch that debugging info. This build uses a newer qt which is more compatible with opeenssl 1.1.x series.
The v4 build should work without any problems. It uses both the newer qt and older-stabler 1.0.x series of openssl. (like v4.1.5 did).
v3: https://github.com/qbittorrent/qBittorrent/issues/10581#issuecomment-489823313
v4: https://github.com/qbittorrent/qBittorrent/issues/10581#issuecomment-491613973

sledgehammer999 on 13 May 2019

Mine keep crashing when starting the app. Have to try multiple times until it can be opened normally. I have to do this every time I wish to open the app. Not sure if it's related but I got plenty of torrents running/seeding.

qBittorrent v4.1.6 (64-bit)
Edition: Windows 10 Pro
Version: 1803
OS Build: 17134.706

gorvinsky on 14 May 2019

Mine was freezing when starting. 4.1.6v4 EXE's fixed the issue :)

Windows 10 Pro [1809, 17763.475]

buszmen201 on 14 May 2019

Mine keep crashing on exit.
Visual Studio Debugger says "Exception thrown at 0x00007FF7AD84DD91 in qbittorrent.exe: 0xC0000005: Access violation reading location 0x000002BCD8AFCA78."
It also ask me to find "qvector.h".

qBittorrent 4.1.6 v4
Windows 10 Home 1803 (64-bit)

matrix934 on 14 May 2019

@IntelliMoo can you try the following build? v4.1.6, Qt5 5.12.3, openssl 1.0.2r
Link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v4.7z

Thanks!
It worked here!

qBittorrent 4.1.6 v4
Windows 10 Pro 1809 (64-bit)
OS build 17763.475

franciscofjs on 15 May 2019

👍1

I can confirm that the v4 fixed the crashes for me (fresh install 4.1.6 originally).
It used to crash after few minutes, now it's been running for 12 hours+.
I'll update again in here in case another crash happen in the coming days

tarkilhk on 16 May 2019

👍1

yes works here too

infr-automation on 16 May 2019

I suspect it is the same as #9667 (comment)
So you'll need to edit C:\Users\<username>\AppData\Roaming\qBittorrent\qBittorrent.ini and change DownloadTrackerFavicon=true to DownloadTrackerFavicon=false save and restart qbt.
Note: You only need to edit the ini _if_ you upgraded from older qbt version. If you did a clean install then no editing is required.

This worked well for me. Thanks for it.

After a few days of issues with this I would like to rescind this. I have had to revert to v4.1.5.

This works for me for a 2-3 days now.

gorvinsky on 16 May 2019

Unfortunately I now have bad news to report about the 4.1.6 v4 version, I've gotten the crashes on exit again a couple of times.

Exception Code: c0000005
Exception Offset: 00000000007f8630
(Dumps attached if helps: CrashDumps.zip)

Seems the longer the app is left running, the greater the chance. Going back to 4.1.5 again unless a new test comes up, thanks. :)

IntelliMoo on 16 May 2019

Is it possible that this program now gets blocked by antivirus software? I had no trouble earlier but today it would 4.1.5 would not start and when trying to update it said i could not write qbittorrent.exe. I could also not install deluge or bittorrent. When I tried unzipping your archive I was not allowed to extract the qbittorrent.exe out of the archive.

ollemonster on 19 May 2019

Is it possible that this program now gets blocked by antivirus software? I had no trouble earlier but today it would 4.1.5 would not start and when trying to update it said i could not write qbittorrent.exe. I could also not install deluge or bittorrent. When I tried unzipping your archive I was not allowed to extract the qbittorrent.exe out of the archive.

I would guess that is due to whatever antivirus software you have getting an update that wrongly "suggests" qBittorrent is bad. Have subsequent antivirus updates fixed the problem? If not, better report it as a false-positive to that antivirus vendor, and in the meantime you can add an exception for qBittorrent easy enough.

IntelliMoo on 21 May 2019

Windows 10 Events Warnings keep appearing when qBittorrent v4.1.6 is running
Profile notification of event Unload for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed, error code is See Tracelogging for error details.
Profile notification of event Load for component {B31118B2-1F49-48E5-B6F5-BC21CAEC56FB} failed, error code is See Tracelogging for error details.

Solution:
Managed to get it running by opening it a couple of times _as Administrator_

christoferd on 21 May 2019

After a few days of issues with this I would like to rescind this. I have had to revert to v4.1.5.

Did you even try build v3 as LittleVulpix quoted above me?

No I did not - I had only used the config changes given. Was updating it in case someone was tracking how many issues were resolved by changing the config.

I have been using this version since the day above and it works well for me.

amaajemyfren on 21 May 2019

My issue was solved with the favicon fix in qbittorrent.ini

Not any more. I don't know why it took so long, but I leave qBT running for days on end. Win7x64, BTW.

I have tried the v4 build linked above, and now it starts, but it crashes on exit. Should I move to #10630 linked above?

TiagoJSilva on 23 May 2019

Well, it's weirder than I expected. I have two folders with one "updated to v4" and second "just exe v4" and first one is crashing on start, but second not...

qBitTorrent:

translations [regular 4.1.6]
- *.qm [regular 4.1.6]
- qbittorrent.exe [v4]
- qbittorrent.pdb [v4]
- qt.conf [regular 4.1.6]
- unist.exe [regular 4.1.6]

qBitTorrent2:

qbittorrent.exe [v4]
qbittorrent.pdb [v4]

buszmen201 on 24 May 2019

Crashing is worse on slower connections. On faster connection sometimes it does not crash.

sirinath on 25 May 2019

It's been a week plus that I haven't encounter a crash so I recommend to try this method which works for me.

gorvinsky on 27 May 2019

It randomly disappears from systray I don't know what triggers the crash. No messages, no warnings

Event log:

Faulting application name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5ccf3300
Faulting module name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5ccf3300
Exception code: 0xc0000005
Fault offset: 0x0000000000aa83e0
Faulting process id: 0x1818
Faulting application start time: 0x01d512a7576e9b44
Faulting application path: C:\Program Files\qBittorrentqbittorrent.exe
Faulting module path: C:\Program Files\qBittorrentqbittorrent.exe
Report Id: 73e6920b-e422-44bf-bba9-ccb2fbac815c
Faulting package full name:
Faulting package-relative application ID:

TTLucian on 31 May 2019

I cam confirm the official build automatically disappears from system tray after sometime. No error messages or anything.

Though it works after restart.

I think you should branch releases at least a week before so that even if you don't have time people can test themselves

jagannatharjun on 1 Jun 2019

I didn't have issues with 4.1.6 initially. Then I started using the RSS (Auto) Downloader. After one night, I checked up how many torrents I had loaded (I have the settings set to "add paused", so it doesn't actually start downloading). Turns out I couldn't but get a glimpse at the number (which was well below 100) before it crashed. Tried deleting the feed in AppData preferences, but it still crashed immediately upon starting (albeit with a longer UI delay).

Reverted to 4.1.5 and no problems with crashing whatsoever. Re-enabling the feed works as well.

YenForYang on 4 Jun 2019

I am having the same issue. I have noticed that it normally happens at times when almost all my bandwidth is being used elsewhere (I have very limited net so a Windows Update or something on another PC can slow every other system to a few kB/s).

Did not have this issue with previous builds.

Faulting application name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5ccf3300
Faulting module name: qbittorrent.exe, version: 4.1.6.0, time stamp: 0x5ccf3300
Exception code: 0xc0000005
Fault offset: 0x0000000000aa83e0
Faulting process id: 0x131c
Faulting application start time: 0x01d52499173f9c99
Faulting application path: C:\Program Files\qBittorrentqbittorrent.exe
Faulting module path: C:\Program Files\qBittorrentqbittorrent.exe
Report Id: ac87068d-e52d-4061-8894-1a11b2e42545
Faulting package full name:
Faulting package-relative application ID:

Ryoken0D on 17 Jun 2019

4.1.6 needs to be pulled until the issue is resolved!

JNavas2 on 19 Jun 2019

👍4

4.1.6 needs to be pulled until the issue is resolved!

We already have a issue for that #10669

ShubhamBelwal on 20 Jun 2019

Hello, I had the issue of crashing at startup. Changing "DownloadTrackerFavicon=false," worked for months. Today it would not work. Downloaded the Link: https://builds.shiki.hu/temp/qbittorrent_4.1.6_x64_for_issue_10581_v4.7z. Did not overwrite files but renamed them instead. When qBittorrent started up, it came up empty, no torrents. Renamed the new files, renamed the old files back and started qBittorrent. All torrents reappeared, and it did not crash. The empty windows also happens when I try to run as Administrator. What can I do to get this work correctly?

1Gofast on 27 Jun 2019

… What can I do to get this work correctly?

Revert to an earlier version (e.g., 4.1.5).
Switch to a different torrent client.

JNavas2 on 27 Jun 2019

😄1

Same here with the 64-bit version of 4.1.6 on 64-bit Windows 10 ultimate. At first, it only 'silent crashed' maybe 3 out of 5 times that I went to launch it. Today suddenly, all the time. 32-bit is fine so I won't bother going back to an earlier version like 4.1.5 - hopefully this is resolved soon.

metronorth on 27 Jun 2019

I can add something to this I think.. I was successfully using the latest public build of 4.1.6 until today, when my system got the following windows update:
"2019-06 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 for x64 (KB4502584)"

after the windows update, it crashes on startup like everyone above. get a windows event ID 1000:faulting application

CEHATX1 on 30 Jun 2019

I tried the 4.1.6 32-bit version, it works, but randomly crashes and leaves a background process running. Sticking with 4.15 until 4.1.7 comes out, I guess.

christianwells11 on 6 Jul 2019

4.1.6 64-bit version crashes just like described above. The weird thing is that only today did this start happening. I'm using an alternative client now but I would like to go on using qBitTorrent since I installed it by choice and it's done a wonderful job until now. Please, fix this bug. Many thanks.

MintHawk on 24 Jul 2019

4.1.6 should have been pulled long ago.
That it's still being distributed is needlessly damaging all around.

JNavas2 on 24 Jul 2019

👍1

I updated to Win10 2016 LTSB x64 this year from Win7 x64 Ultimate. Old 2002 apps, everything... works great. I started using qBittorrent with Win10 for 'Bind to Device/IP' option. Both 4.1.5 and 4.1.6 work flawlessly downloading torrents. 4.1.5 had an issue moving UI down at little at every restore. 4.1.6 sometimes crashes at closing, needing to wait 10 seconds to see if errors before closing VPN. I'm awaiting next version, maybe 4.2.0 ?

theswagler on 24 Jul 2019

CEHATX1- You've just exposed the primary issue. Programmers need to get away from dependency on .NET Framework, and get back to programming in assembly and unmanaged C++. Look at the size of modern apps utilizing .NET and other higher level languages, it's absurd. Add quagmire of dependent libraries, along with MS forced Beta updates, and probability for incompatibility and errors is inevitable.

theswagler on 24 Jul 2019

CEHATX1- You've just exposed the primary issue. Programmers need to get away from dependency on .NET Framework, and get back to programming in assembly and unmanaged C++. Look at the size of modern apps utilizing .NET and other higher level languages, it's absurd. Add quagmire of dependent libraries, along with MS forced Beta updates, and probability for incompatibility and errors is inevitable.

With respect, that would be a giant leap _backward_ that would just make things _worse_, but this is _not_ the place to debate the issue.

JNavas2 on 24 Jul 2019

JNavas2- I didn't mean to rile anyone, just an old-school C++ programmer's two-cents.
In your opinion, which latest version is the best?

theswagler on 24 Jul 2019

@theswagler Sure, no offense taken, none intended.

I currently use and recommend qBittorrent 4.1.5 64-bit on Windows 8.1 Pro.

FWIW, I cut my software teeth on Autocoder (like Assembler). I can now program in well over 100 languages. I've taught software engineering and quality management; I've managed large, complex software projects; and I've released public Android apps.

My principal objections to assembler and C++ include lack of checking and typing. My current language recommendation would be Rust.

JNavas2 on 24 Jul 2019

JNavas2- I'm a mech/arch designer that enjoys C++ as a hobby.
Here's apps I've written since 2004: https://swaglertools.cf/
My flagship is Image Draw, it utilizes GDI+ to create 2D layered projects similar to Photoshop, but in a CAD environment.

theswagler on 25 Jul 2019

👍1

To me 4.1.6 runs.... for a while. After a random period of time (like half an hour) I eventually notice the qB icon is gone from the tray, and that's it. Happens on at least 2 Win10 1903 instances. Can't say anything about earlier versions coz I don't have any.

bviktor on 2 Aug 2019

I rolled back to v4.1.5 too. I tried v4.1.4, but it drops window down on
close like v4.1.5. It's not worth my time to test more previous versions,
so I'll stay with v4.1.5 until next release.

On Fri, Aug 2, 2019 at 12:16 PM bviktor notifications@github.com wrote:

To me 4.1.6 runs.... for a while. After a random period of time (like half
an hour) I eventually notice the qB icon is gone from the tray, and that's
it. Happens on at least 2 Win10 1903 instances. Can't say anything about
earlier versions coz I don't have any.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/qbittorrent/qBittorrent/issues/10581?email_source=notifications&email_token=AF6FBGY6Q3J4CXMXB62XM7LQCSBXTA5CNFSM4HK5GAAKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3OTTVA#issuecomment-517814740,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF6FBGY2QGC2SGZD32LT4P3QCSBXTANCNFSM4HK5GAAA
.

theswagler on 2 Aug 2019

The problem most probably lies with the usage of openssl 1.1.x series.
I released v4.1.7 and it uses the 1.0.x series of openssl. This should fix all your crashes.

sledgehammer999 on 4 Aug 2019

Thanks, let's hope it's actually fixes now. SmartScreen doesn't like this version btw.

bviktor on 4 Aug 2019

openssl ? Yup, external libraries. I hope it fixes issues. I really like the bind to IP feature, and it downloads quicker than uTorrent on my sorry CenturyLink DSL service out in sticks.

theswagler on 4 Aug 2019

@sledgehammer999 just confirming two things.

no silent crashes with 4.1.7 reported in eventmanager
no crashes either with an alpha build of 4.2.0 [been using/testing that since I came across it in June] that glassez compiled in torrent rechecking thread. (that used openssl 1.1.1.c & qt 5.13)

quick question regarding 4.1.7 - does that address the low security issue in openssl (CVE-2019-1552)
https://www.openssl.org/news/secadv/20190730.txt

Note

OpenSSL 1.0.2 and 1.1.0 are currently only receiving security updates.
Support for 1.0.2 will end on 31st December 2019. Support for 1.1.0
will end on 11th September 2019. Users of these versions should
upgrade to OpenSSL 1.1.1.

xavier2k6 on 4 Aug 2019

The problem most probably lies with the usage of openssl 1.1.x series.

@sledgehammer999 could you add some more info on this and why you suspect openssl to be the cause?

Piccirello on 4 Aug 2019

The problem most probably lies with the usage of openssl 1.1.x series.

@sledgehammer999 could you add some more info on this and why you suspect openssl to be the cause?

@Piccirello If you look through the comments - I had previously pointed out that at the time QT 5.12.x had not fully implemented support for OpenSSL 1.1.1 series......it became fully compliant in 5.12.4 & 5.13.

https://blog.qt.io/blog/2019/06/17/qt-5-12-4-released-support-openssl-1-1-1/

Also - I have confirmed that there's no crashes with a test build of 4.2.0 which uses Qt 5.13 & OpenSSL 1.1.1c

xavier2k6 on 4 Aug 2019

4.1.7 has seemed to have crashed as well now

christianwells11 on 17 Aug 2019

4.1.7 has seemed to have crashed as well now

@christianwells11 can you give some more details....are you getting a silent crash (logged in event viewer) or an actual crash with debugging info?!

Did you also try:
https://github.com/qbittorrent/qBittorrent/issues/10581#issuecomment-489549035

xavier2k6 on 17 Aug 2019

I can confirm v4.1.7 is working great on Win10 2016 LTSB. No window movement at minimize, and no (2) popup dialogs informing crashing after closing,

theswagler on 18 Aug 2019

To all of you who 1) had crashes with official v4.1.6, 2) then didn't have with the build I provided of 4.1.6 using openssl 1.0.2 and 3) don't have crashes with official v4.1.7

can you try the following build? It is 4.1.7 using the exact same lib versions as the official but openssl is 1.1.1c. Do you start having crashes?

Link: http://builds.shiki.hu/temp/qbittorrent_4.1.7_x64_for_issue_10581.7z

sledgehammer999 on 25 Aug 2019

Working so far.

christianwells11 on 26 Aug 2019

I‘m using official v4.1.7,but it crashed several times, maybe too many torrents?

xxn1202 on 30 Aug 2019

@xxn1202 can you provide some more info please......silent crashes ie as in logged in event viewer or actual crashes......debug window showing with crash report?

xavier2k6 on 31 Aug 2019

Experiencing the same with v4.1.7

Win 10 Pro 1903 / OS build 18362.295

After killing the unresponsive task then restarting and waiting 5 minutes or so, program begins responding. Note, I have many torrents partially complete which are very large (50+ gb) and around 20 other misc. Think it may be just scanning.

jjaaccoobb on 9 Sep 2019

I'm so sorry that the crash happened several weeks ago, I could not find the crash report. If the crash happened again ,I will tell you in the first time.

在 2019-09-01 05:26:59，"xavier2k6" notifications@github.com 写道：

@xxn1202 can you provide some more info please......silent crashes ie as in logged in event viewer or actual crashes......debug window showing with crash report?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

xxn1202 on 9 Sep 2019

Can't upgrade to 4.1.8 on Win10 1903 OS Build 18362.356. I'm getting:

Windows protected your PC
Windows Defender SmartScreen prevented an unrecognized app from starting. Running this app might put your PC at risk.
App: | qbittorrent_4.1.8_x64_setup (1).exe
-- | --
Publisher: | Unknown publisher

For both 64 and 32-bit installers.

Krumpet on 26 Sep 2019

Just a quick thing to check for everyone having issues just launching the app. make sure you run as Admin otherwise for me it looks like it want to open but just closes itself.

Trefle10 on 4 Jan 2020

Original issue report and most comments pertain to an issue that was already fixed, see
https://github.com/qbittorrent/qBittorrent/issues/10581#issuecomment-518017172 and https://github.com/qbittorrent/qBittorrent/issues/10581#issuecomment-518038444

All others still experiencing crashes in the latest version please submit a new issue with stacktrace as they are most likely related to something else.

FranciscoPombal on 19 Feb 2020

Qbittorrent: 4.1.6 not working on my Windows 10

qBittorrent version and Operating System

If on linux, libtorrent and Qt version

What is the problem

What is the expected behavior

Steps to reproduce

Extra info(if any)

Most helpful comment

All 140 comments

4.1.6 needs to be pulled until the issue is resolved!

4.1.6 needs to be pulled until the issue is resolved!

Note

Related issues