Crash Exception code: 0xc0000409 Windows Server 2012 R2 as Unraid VM #13143
Comments
|
@skidaddl3 can you try build below: Windows test build of 4.3.0(Alpha1) with listed libraries: "Windows Test Build" download link below: Is your memory overclocked? Did you check your memory? How to Test Your Computer’s RAM for Problems |
|
I will try your suggestion. |
|
Just crashed. I left it running maximised (in the foreground). |
|
Do you have mapped network drives? Perhaps some that might not always be available as well? |
|
@FranciscoPombal I've been reviewing 0xC0000409 errors here on qBittorrent tracker. It seems this issue is localized to just the 64bit version of qBittorrent may have something to do with OpenSSL? - ref: #9865 (comment) 1st reported instance was way back in (2013) with qBittorrent 3.0.9 on windows 7 64bit Home in #558 but didn't raise it's head again until (2018) - Perhaps, @skidaddl3 could use one of your builds so we could see if the issue lies in the way OpenSSL is compiled? EDIT: also, it seems the portableapps version seems more susceptible to this type of error......a clean profile as mentioned in another thread seems to not exhibit this issue. EDIT: Interesting -> openssl/openssl#1592 |
|
@skidaddl3 next time #13143 (comment) appears or you reproduce, can you provide the details (copy/paste) what's in the scrollable window please? |
|
Thank you for your help, in any case! I'm sure others experiencing this appreciate it too.
Yes, it is an Unraid SMB share:
No dramas, I'll attempt to provide this when it occurs. I also tried looking for some kind of dump, however that the memory is 30GB, I wouldn't want to sieve through such data or be uploading it somewhere. I suppose I could/should lower that ceiling anyway... |
|
And as I was writing the previous reply, QB has crashed. Here is the crash text: |
|
I have reverted to 4.2.5 for now, because I think the beta had an issue with the Web UI connection profile as I couldn't connect on a remote computer. Even after re-setting the username/password. Edit: Well the Web UI connection issue was to do with the Windows Firewall incoming rules, because I placed the 4.3.0(Alpha1) executable in a subfolder of qbittorrent's program file folder. (facepalm) Maybe there is some correlation with that webui connection, automatically adding torrents and the amount already in qbittorrent? I will check with a two-day run at least, after I find that the stack trace occurs in version 4.3.0(Alpha1) |
|
@skidaddl3 unfortunately, there's nothing in that info that's helpful from what i can see. Please download & install Debug Diagnostic Tool v2 Update 3 (It would be great if you could do this for 4.2.5 build & 4.3.0alpha master build, if not too much hassle) Download & extract these predefined rules Run DebugDiag 2 Collection from your start menu. This will hopefully help point us in the right direction to where there's a problem in the program. Your memory usage will probably increase more so than normal & the program itself may become unresponsive for a period of time due to having a debugger attached. As soon as a stacktrace is created, it will be ok to deactivate the rules & close/detach the debugger from qBittorrent |
|
Possibly related to #13138, #13069. Such builds are here:<removed inactive link to build it was a build of 83f1028 with the following patch on top>: diff --git a/src/base/bittorrent/session.cpp b/src/base/bittorrent/session.cpp
index af6df18ae..c1a36ce1f 100644
--- a/src/base/bittorrent/session.cpp
+++ b/src/base/bittorrent/session.cpp
@@ -4718,7 +4718,7 @@ void Session::handleStateUpdateAlert(const lt::state_update_alert *p)
void Session::handleSocks5Alert(const lt::socks5_alert *p) const
{
if (p->error) {
- LogMsg(tr("SOCKS5 proxy error. Message: %1").arg(QString::fromStdString(p->message()))
+ LogMsg(tr("SOCKS5 proxy error. Message: %1 | error.message(): %2").arg(QString::fromStdString(p->message()), QString::fromStdString (p->error.mess 16 age()))
, Log::WARNING);
}
}
diff --git a/src/base/bittorrent/torrenthandleimpl.cpp b/src/base/bittorrent/torrenthandleimpl.cpp
index 062ec56a7..09ddee2da 100644
--- a/src/base/bittorrent/torrenthandleimpl.cpp
+++ b/src/base/bittorrent/torrenthandleimpl.cpp
@@ -1417,6 +1417,9 @@ void TorrentHandleImpl::handleTrackerErrorAlert(const lt::tracker_error_alert *p
m_trackerInfos[trackerUrl].lastMessage = message;
+ LogMsg(tr("<tracker_error_alert> error: %1 | failure reason: %2")
+ .arg(QString::fromStdString(p->error.message()), p->error_message()), Log::WARNING);
+
// Starting with libtorrent 1.2.x each tracker has multiple local endpoints from which
// an announce is attempted. Some endpoints might succeed while others might fail.
// Emit the signal only if all endpoints have failed. |
Last night, QB did take a very long time to load to the point I left it, without the UI showing up. Now the UI is showing, it does appear to be running slow (even transfer speeds showing low speeds ~40KB/s, expect 5MB/s). I try interacting with transfers and nothing appears to be happening, no response. I am running version 4.2.5 with the debugger. Oh and as I was writing this, the right click Properties list has shown up.
I am going to reboot my Unraid server, because it is reporting strange behaviour. After, I will re-run the debugging process. |
Could be related, as I do use mapped network drive and Sonarr, Radarr and Lidarr |
|
I haven't seen a crash report of QB, but I have restarted the server a couple of times. I have checked the DebugDiag log folder and there are 4 text files in there. Please find the logs here. I think there are some Stack Traces there. |
|
@skidaddl3 only 2 stack traces there from what I can see, which none are of So, you will have to test/try to reproduce for a bit longer I'm afraid. |
No problem. I figured that much, seen as there was no crash that I noticed. |
|
Posting stack traces here for clarity: click to expand Exception 0XE06D7363 stack trace with qBittorrent 4.2.5click to expand Exception 0X000006BA stack trace with qBittorrent 4.3.0 |
Hopefully, if not too much to ask - I'd like to get a stack trace of In time, I may get you to run another build with different |
|
I'm running 4.2.5 until I get the 0xC0000409 code. I'll get onto 4.3.0 after (once we know we have it I guess) |
|
The debugger will grab the stack trace whenever it happens anyway as long as it's still attached to the qBittorrent process. |
|
Ok, so after leaving it run overnight, I notice it is still running (via task manager. CPU% fluctuates) where the occasional notification from qbittorrent mentions I/O error (most likely about not enough space but that info is always truncated). |
|
@skidaddl3 try enabling |
No such parameter "memorycompression" |
|
did you type as is: |
|
|
|
please try |
|
PS C:\Users\Administrator> Get-MMAgent ApplicationLaunchPrefetching : False It looks like the memory compression parameter doesn't exist from looking at the help contents of the command: NAME SYNOPSIS SYNTAX |
|
I have dropped the ram max for the vm since this morning. |
Sorry, I should have said that I installed the fresh Windows Server 2012 R2 Standard OS. I think it was running bad like before, due to DebugDiag rule activated before qbittorrent has been started. Qbittorrent runs fairly smooth, if I activate the rule AFTER starting qbittorrent. |
New crash dump uploaded with PID 3932 to match log |
Was that using the build from https://github.com/FranciscoPombal/qBittorrent/suites/890570460/artifacts/10579779? |
Yes. I installed qbittorrent 4.2.5 (because it was a fresh OS install), migrated old qbittorrent appdata to retain torrent progress and did as per
|
I did not use the config file that comes with that build however... |
|
@skidaddl3 that's fine - thanks for clarification, seems that build is missing something for the purpose of debugging but have the stacktrace from log.
EDIT: @FranciscoPombal Any idea why above would happen for your build? (My build/official build seem to load Please go ahead & de-activate the rules, detach the debugger from qBittorrent - should have enough of info gathered now from across 3 builds which use various Will report back here with findings. (may be a few days) |
|
@skidaddl3 as for |
|
I will keep an eye on released update for qb I will check if there are any relevant hotfixes when I get a chance. I doubt the server OS is not up to date |
|
@skidaddl3 haven't forgot about this, I still need to fully go through dumps/logs - in the meantime can you try build below: (This build should get rid of Hopefully, you'll be able to confirm the above?! Windows test build of 4.3.0(Alpha1) with listed libraries: |
|
@xavier2k6 no problem. It has been a busy week for myself too. |
|
Running qb with debugger now. Was busier than expected. |
|
New crash dump uploaded with PID 3720 to match log |
Thanks, looks like the build referenced in #13143 (comment) doesn't fix In relation to |
|
No peers manually banned AFAIK |
|
I am still interested in a fix. Was there any progress/news? |
|
@skidaddl3 no progress as such.....will provide another test build when I can. |
|
@xavier2k6 hi, sorry I missed your last test build download. I hope that makes sense. |
|
Thanks for the feedback, I'd advise to keep this Open for now. |
|
I just had one of these crashes, to which I have never seen before: qBittorrent has crashed qBittorrent version: v4.2.5 (64-bit) Caught signal: SIGSEGV
|
|
@skidaddl3 This may be fixed with 4.3.0.1. Mind trying it out? |
@FranciscoPombal thank you, qBittorrent prompted me to upgrade to 4.3.0 two days ago and yesterday I upgraded to 4.3.0.1 On version 4.3.0 I was getting a lot of torrents erroring out with a network error. I shall see how we go. My previous comment I usually check QB once a day. Edit: Version 4.3.0.1 |
|
"Errored: An unexpected network error occurred" qBittorrent remains to do a bunch daily. It typically shows up in a bunch. I have searched Google and there are other users with Network Shares that experience the same issue.
|
|
Just had a crash after leaving qBittorrent for about 4 days. Problem signature: |
|
@skidaddl3 be great if you could get a new crash dump/stack trace with 4.3.0.1
That's more than likely a conflict in your network setup! |
|
@xavier2k6 and @FranciscoPombal So my testing is no longer valid for the Windows Server 2012 R2 qBittorrent version and I am sunsetting it. Again, cheers for the effort! |
|
Thank you for your participation. If anyone else can reproduce this and shed more light into this in the future, please open a new issue report. |
qBittorrent version and Operating System
4.2.5
Windows Server 2012 R2
If on linux, libtorrent-rasterbar and Qt version
N/A (Unsure if Unraid is relevant)
What is the problem
Crash Exception code: 0xc0000409 when right click on UI after several hours of Qbittorrent working. The UI does stuggle to open upon launching Qbittorrent too. To show UI, typically after about a minute righ clicking on the system tray icon helps to left click and focus the UI to the desktop (show the UI)
What is the expected behavior
No crashing
Steps to reproduce
As per the problem
Extra info(if any)
No SFC integrity violations, DISM also found no problems.
I have a feeling it is to do with Unraid's shared folder design, as I am using a Cache SDD drive and it is technically full. I am getting a lot of "...not enough space on the disk" file error alerts in QB log, however I have set the Unraid shared folder for Qbittorrent's "working directory" as 'Prefer'. The problem is a 2TB Cache SSD seems not to be enough and I also set Qbittorrent to "Pre-allocate disk space for all files" to avoid a different kind of congestion.
Process memory priority: Normal
Save resume data interval: 3 min
Recheck torrents on completion: enabled
Transfer list interval: 1000ms
Async I/O threads: 512
File pool size: 40
I have recently reduced the "Outstanding memory when checking torrents" from 1024MiB to 64MiB
Disk cache: -1 (Auto)
Cache expiry interval: 60s
Enable OS cache: enabled
Coalesce reads & writes: enabled
Piece extent affinity: disabled
Everything else should be stock, standard.
The text was updated successfully, but these errors were encountered: