qBit 3.1.9 exe runtime error

[fusk]

[quote="sledgehammer_999"]
Ok here is the new patched version: http://builds.shiki.hu/temp/qbittorrent ... _setup.exe
[/quote]

Used the latest one you posted.

[sledgehammer_999]

I suppose you tested the mingw one too before going to the latest one, right? And it showed the same bug...

Try setting the cache to 1GB instead. And see if that helps.

EDIT: I''ll provide an exe built with the MSVC compiler. This will allow you to run it through WinDbg and get useful info.

[sledgehammer_999]

Ok. Here is a new patched msvc build.

1. Run WinDbg and attach to the process
2. When it crashes run !analyze -v
3. Don't change the cache to 1GB. Leave it the same as the other times you had the problem.

http://builds.shiki.hu/temp/qbittorrent ... _setup.exe

[ciaobaby]

The memory setting is the cache size where BitTorrent clients store the downloaded blocks before committing them to disk, and contrary to popular belief and countless "Speed up your BitTorrent" You Tube videos, ... having a huge cache is a LESS THAN an efficient way to use resources.

BitTorrent clients handle data in blocks which are 16kiB (16384 Bytes) in size and depending on how many active downloads you run at any one time probably only need to reserve space for 15 - 20 blocks at any one time so 256kiB - 384kiB is more than enough reserved cache. Going bigger than that is wasteful of memory and can overload the drive write queue (uTorrent's legendary disc overload)

And as you have seen if qBT's (or ANY other 32bit client) memory usage (which includes the reserved cache space)  hits 1.8 GiB the result IS a catastrophic failure.

[fusk]

Yes, i do remember that from utorrent if cache is set to 1.8gb that it would crash a lot. But i don't understand why allow a value you know is going to mess your program up.
I understand how you might see it as a waste of resources, but i do have 8gb ram, and i paid for it, i see it as waste of hardware not to utilize it, however, i do not need 2gb cache. Around 1.2gb is fine for me, then everything seems to be running smooth even with high bandwidth and many active torrents.

[sledgehammer_999]

Why make ONE program use all the RAM when you can have MULTIPLE programs use it and fill it? IMO its better for every program to use as little as possible so you can run as many programs as you need concurrently.

Btw, what is your status? Are you going to test my last build through the debugger and 2gb cache or just lower your cache and be done with it?

[Nemo]

Maybe a weird suggestion but could he maybe try Dayman's build of v3.1.9 which is 64-Bit and see if it still crashes or does that not matter? Just an idea .

[ciaobaby]

[quote="sledgehammer_999"]
Why make ONE program use all the RAM when you can have MULTIPLE programs use it and fill it? IMO its better for every program to use as little as possible so you can run as many programs as you need concurrently.[/quote]

Exactly! No matter how much RAM you have in your machine, dedicating a large chunk of to one application is NOT making use of it, especially when it is dedicated to an application that cannot actually make use of it

[fusk]

Well, this isn't a work machine, so even if qbit were to use 2gb of ram while i was running all the other stuff i do there would still be memory left to spare.
This machine is all play. Right now i'm running all the programs i use, qbit is using 300mb for a total of 3.7gb used.
The reason i'm using a higher than normal cache is because it seems to run better when there's a lot going on, 50+ active torrents, 400mbit+ or maybe i'm just imagining things.

[ciaobaby]

The reason i'm using a higher than normal cache is because it seems to run better when there's a lot going on, 50+ active torrents, 400mbit+ or maybe i'm just imagining things.

Then the best setting for your use case is 0 and qBT will adjust the cache size to suit what it needs at the time. If there are a lot of blocks in transit it will use more memory and when it doesn't need it, it will be released back to the 'free' memory pool.

[sledgehammer_999]

@fusk I hope you are not ignoring me. Please answer my last question.

PS: If you want to use more than 2GB of RAM you could try using Dayman's builds. They are 64bit and should be able to handle a lot of RAM. link-> http://qbforums.shiki.hu/index.php/topic,1645.0.html

[fusk]

I installed the latest one you posted http://builds.shiki.hu/temp/qbittorrent ... _setup.exe
But nothing has happened so far.

[sledgehammer_999]

[quote="fusk"]
I installed the latest one you posted http://builds.shiki.hu/temp/qbittorrent ... _setup.exe
But nothing has happened so far.
[/quote]

ok. I hope you didn't change your cache settings. Leave it at whatever you had set it previously.

[fusk]

Okay, got I/O error but windbg doesn't stop as it did before with exe crash, it just continues to run. I resumed the torrents with no problems, program didn't crash, however, the I/O errors do continue afterwards like every 2 min, and seems to happen on a random number of torrents, from 1 to 6 torrents so far.
This is literally 2 secs before it happens.



Edit:
Went to open statistics and then it crashed.

GetPageUrlData failed, server returned HTTP status 404
URL requested: http://watson.microsoft.com/StageOne/qb ... Retriage=1

FAULTING_IP:
qbittorrent!QNativeImage::QNativeImage+102
013c4a56 8b4010          mov    eax,dword ptr [eax+10h]

EXCEPTION_RECORD:  ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 00000000013c4a56 (qbittorrent!QNativeImage::QNativeImage+0x0000000000000102)
  ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
  Parameter[0]: 0000000000000000
  Parameter[1]: 0000000000000010
Attempt to read from address 0000000000000010

FAULTING_THREAD:  0000000000000ce0

PROCESS_NAME:  qbittorrent.exe

ADDITIONAL_DEBUG_TEXT: 
Use '!findthebuild' command to search for the target build information.
If the build information is available, run '!findthebuild -s ; .reload' to set symbol path and load symbols.

FAULTING_MODULE: 0000000077120000 ntdll

DEBUG_FLR_IMAGE_TIMESTAMP:  5325f10f

ERROR_CODE: (NTSTATUS) 0xc0000005 - Instruktionen ved 0x%08lx refererede hukommelse ved 0x%08lx. Hukommelsen kunne ikke %s.

EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - Instruktionen ved 0x%08lx refererede hukommelse ved 0x%08lx. Hukommelsen kunne ikke %s.

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  0000000000000010

READ_ADDRESS:  0000000000000010

FOLLOWUP_IP:
qbittorrent!QNativeImage::QNativeImage+102
013c4a56 8b4010          mov    eax,dword ptr [eax+10h]

MOD_LIST: <ANALYSIS/>

BUGCHECK_STR:  APPLICATION_FAULT_NULL_CLASS_PTR_DEREFERENCE_INVALID_POINTER_READ_WRONG_SYMBOLS_ZEROED_STACK

PRIMARY_PROBLEM_CLASS:  NULL_CLASS_PTR_DEREFERENCE

DEFAULT_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE

LAST_CONTROL_TRANSFER:  from 000000000129a89e to 00000000013c4a56

STACK_TEXT: 
0039d04c 0129a89e 16db4490 00000111 0000018b qbittorrent!QNativeImage::QNativeImage+0x102
0039d0b4 0129a793 1a4bdec8 00000004 0529f288 qbittorrent!QRasterWindowSurface::prepareBuffer+0x99
0039d0cc 01296e2a 0039d1c4 832672d2 00000000 qbittorrent!QRasterWindowSurface::setGeometry+0x69
0039d224 01296bcd 0029f278 05308518 097f5e60 qbittorrent!QWidgetBackingStore::sync+0x257
0039d240 01158124 097f5e60 0039d294 00000000 qbittorrent!QWidgetBackingStore::sync+0xf4
0039d254 0126da8d 0039d294 83267206 00000000 qbittorrent!QWidgetPrivate::syncBackingStore+0x33
0039d2f0 0126ae50 097f5e60 0039d36c 00000001 qbittorrent!QETWidget::translatePaintEvent+0x132
0039d500 759462fa 002904b0 0000000f 00000000 qbittorrent!QtWndProc+0xda2
WARNING: Stack unwind information not available. Following frames may be wrong.
0039d52c 75947316 0126a0ae 002904b0 0000000f USER32!gapfnScSendMessage+0x332
0039d5a4 75946de8 00000000 0126a0ae 002904b0 USER32!GetDC+0x52
0039d600 75946e44 01ee6c90 00000000 0000000f USER32!GetThreadDesktop+0x185
0039d63c 7731010a 0039d654 00000000 0039d6a8 USER32!GetThreadDesktop+0x1e1
0039d6b8 7594788a 0126a0ae 00000000 0039f474 ntdll_77300000!KiUserCallbackDispatcher+0x2e
0039d6c8 0150a4dd 0039d6f4 8326762e 017a97ac USER32!DispatchMessageW+0xf
0039f474 01269cb4 00000024 0039f4c8 0150217c qbittorrent!QEventDispatcherWin32::processEvents+0x481
0039f480 0150217c 00000024 0039f4e4 0039f498 qbittorrent!QGuiEventDispatcherWin32::processEvents+0x13
0039f490 01502262 00000024 8326543e 017a97ac qbittorrent!QEventLoop::processEvents+0x38
0039f4c8 014b5adf 00000000 8326540a 017a97ac qbittorrent!QEventLoop::exec+0xe1
0039f4fc 010890af 832655fe fffffffe 0039f7f4 qbittorrent!QCoreApplication::exec+0x99
0039f7d4 0153daca 00000001 00f0be00 00000000 qbittorrent!main+0xf93 [c:\qbittorrent\qbittorrent\src\main.cpp @ 389]
0039f7f8 016e0985 00ff0000 00000000 00412b8d qbittorrent!WinMain+0xac
0039f888 76d7336a 7efde000 0039f8d4 77339f72 qbittorrent!__tmainCRTStartup+0x113 [f:\dd\vctools\crt_bld\self_x86\crt\src\crt0.c @ 263]
0039f894 77339f72 7efde000 77793388 00000000 KERNEL32!BaseThreadInitThunk+0x12
0039f8d4 77339f45 016e09f0 7efde000 00000000 ntdll_77300000!RtlInitializeExceptionChain+0x63
0039f8ec 00000000 016e09f0 7efde000 00000000 ntdll_77300000!RtlInitializeExceptionChain+0x36


SYMBOL_STACK_INDEX:  0

SYMBOL_NAME:  qbittorrent!QNativeImage::QNativeImage+102

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: qbittorrent

IMAGE_NAME:  qbittorrent.exe

STACK_COMMAND:  ~0s ; kb

BUCKET_ID:  WRONG_SYMBOLS

FAILURE_BUCKET_ID:  NULL_CLASS_PTR_DEREFERENCE_c0000005_qbittorrent.exe!QNativeImage::QNativeImage

WATSON_STAGEONE_URL:  http://watson.microsoft.com/StageOne/qb ... Retriage=1

Followup: MachineOwner

& here is top to bottom http://paste.ubuntu.com/7110010/

[fusk]

Just out of curiosity, did that info do anything for you ?