-
-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exception 0XE06D7363 - 4.2.0 Test Build #11661
Comments
Got another one with a different test build & seems to be Qt related again qbittorrent__PID__10756__Date__12_27_2019__Time_11_11_36PM__516__Log.txt 4.2.0 Test Build on Windows 10 Pro x64 Build 18363.535 (November Update 1909) also logged a 0X000006BA & a 0XC0000005 exceptions in same session as well as 2 crashes sigsegv/sigabrt on close.....
|
qBittorrent version: v4.2.1 (64-bit) Caught signal: SIGABRT
|
qBittorrent version: v4.2.1 (64-bit) Caught signal: SIGSEGV
|
@arvidn |
the crash here seems to be an issue in libtorrent. But the details about that crash also seem to be swallowed by qBTs crash handler, which itself then crashes. I suppose that if qbt either didn't have a crash handler, or if it didn't crash (but perhaps reported more details in a crash report) it would be easier to understand what's going on in libtorrent. Whatever it is, it happens when destructing a vector of this seems to be a similar issue in libtorrent, except this time the crash handler in qBT doesn't seem to crash, instead it appears to resume the GUI thread (which is bound to fail, it shouldn't be done this way). The GUI thread tries to interact with the session object, which is still inside its destructor (that's what failed in the first place). The underlying issue appear to be in libtorrent, but qBT doesn't handle the crash reporting correctly either. I say "appear" because a data structure in libtorrent appear to be corrupt. What caused the corruption is impossible to say (just based on the stack trace). Does anyone have the ability to make a windows build with sanitizers enabled? specifically address sanitizer. There are other, older and less precise, tools for windows too, like gflags. I haven't used gflags in 5 or 6 years, but I think you run something like:
this crash also suggests heap corruption of libtorrent data structures. I really think testing with page-heap ( |
may be of some help: |
Using DebugDiag for stacktraces which allows rules/exceptions to be created/exported etc. |
@arvidn I can set page heap flags with debugdiag too (I totally overlooked this option?! Edit: Have turned on/enabled "Enable Full PageHeap" now & will report back if I encounter any more issues with stack traces etc. |
Exception 0X000006BA All picked up by debugdiag (see log) (no crash etc) sfc /scannow etc shows no issues...... qbittorrent__PID__3396__Date__01_03_2020__Time_11_11_20AM__796__Log.txt |
afaict, that seems to be an uncaught exception originating from Qt, no libtorrent involved. |
Action limit of 1 reached for Exception 'E06D7363::'. qbittorrent__PID__1176__Date__01_15_2020__Time_04_46_24PM__751__Log.txt |
This is happening on a self-compiled version of 4.3.0alpha1: It is also now reproducible!! Manually ban (Thunder/XunLei -XL0012-) peer permanently in the peers tab. |
Manually ban (Thunder/XunLei -XL0012-) peer permanently in the peers tab. Is definitely reproducing this for me, these peer id's are using special characters/symbols. |
@sledgehammer999 this is reproducible. Also, I wonder would it be a good idea to compile with "/EHa" via Exception Handling Model |
@xavier2k6 you might want to track arvidn/libtorrent#4345 that I just opened. It might provide a clue on these crashes. |
@sledgehammer999 user @BattouSaeen has experienced this issue too. Posting stack traces/info from associated logs from #12064 here Associated logs:
|
arvidn/libtorrent@53c2647 may have actually fixed this, as another user experienced this kind of exception in #13143 - I will wait for confirmation before closing. |
Closing this as I can't reproduce after fix from arvidn/libtorrent#4922 I certainly hadn't got it since! I believe the user in #13143 may have used the wrong build?! |
Please provide the following information
qBittorrent version and Operating System
4.2.0 Test Build on Windows 10 Pro x64 Build 18363.535 (November Update 1909)
If on linux, libtorrent-rasterbar and Qt version
(N/A)
What is the problem
(Exception 0XE06D7363)
What is the expected behavior
(To not encounter exception)
Steps to reproduce
(N/A)
Extra info(if any)
The text was updated successfully, but these errors were encountered: