Jump to content
Comet Forums
blackps

BitComet Crashes After Completion of a Task

Recommended Posts

Are you using a local disc drive, or external? and is bitcomet set to initiate a virus scan upon completion of a task?

Share this post


Link to post
Share on other sites

Local disk,i have a antivirus ( avast 6 ) but i did not set bitcomet to scan task on finish, another problem is that i can't report the crash , see pic.

post-59166-13168762312426.jpg

Edited by blackps (see edit history)

Share this post


Link to post
Share on other sites

Check and see if bitcomet set up a scan upon completion, if so, uncheck that option. Also, do you have it set to do a redundant hash check when task completes? and does it crash on every task? only on torrents? or is it intermittent?

ps. are you using any IP filtering programs like peerguardian/peerblock or protowall?

Share this post


Link to post
Share on other sites

Check and see if bitcomet set up a scan upon completion, if so, uncheck that option. Also, do you have it set to do a redundant hash check when task completes? and does it crash on every task? only on torrents? or is it intermittent?

ps. are you using any IP filtering programs like peerguardian/peerblock or protowall?

I don't use peerguardian/peerblock or protowall , i have found the bug that cause the bitcomet to crash,it's the new implantation bittorent.hash_check_if_file_changed, because with the option Add .bc! file extension to unfinished file it will crash after download complete because BitComet will hash check the file on finish, ( he thinks the file has changed because on task complete it will remove .bc! extension) i hope you understand what i`m trying to see my English is not the best, unselecting the option Add .bc! file extension to unfinished file has resolved my bug, it was crashing only on some tasks not all,this is the bug from bitcomet as he thinks all files changed after download because of the .bc! extension with option bittorent.hash_check_if_file_changed. It was crashing when download finished on file http://thepiratebay.org/torrent/6697893/TuneUp_Utilities_2012_12.0.600_Beta_6_Multilingual_Portable , Thanks for the help and hope it will help you fix the bug.

The bug will happen only if you have enable bittorent.hash_check_if_file_changed and Add .bc! file extension to unfinished file ,disabling one will fix the bug.

v1.26 2011.01.27

GUI Improved: improve text information displayed in VIP acceleration dialog

GUI Improved: improve progress bar of disk space in task properties dialog

GUI Improved: new setting in advanced option page to enable/disable auto hash check after downloaded file changed <==== THIS IS THE BUG THAT CAUSE THE CRASH , starting 1.26 + Add .bc! file extension to unfinished file ,will cause the crash.

The fix will be like this

Not scan the file if the .bc! extension has been removed as it's the same file.

Edited by blackps (see edit history)

Share this post


Link to post
Share on other sites

The same crash if you enable hash check file on finish. I think it's antivirus related ,but it's crashing only with the 2 options i have told you about,i`m using Avast Internet Security 6,ask other people if they have antivirus as i see i`m not the only one who has the crashing problem,Thanks.

Edited by blackps (see edit history)

Share this post


Link to post
Share on other sites

The option to add .bc! and for final hash check have existed for a good long while, over 50 versions so I don't think this is the cause. Harddrive and/or file system errors could cause this, or improper initiation of an antivirus scan. I asked you to check to confirm a/v scan wasn't enabled in bitcomet, it's in the options, if you can't find it, I'll point you to it.

I might be slow to reply the next few days, My computer is in pieces and I've been using an old dinosaur that can barely open one page at a time.

Share this post


Link to post
Share on other sites

The option to add .bc! and for final hash check have existed for a good long while, over 50 versions so I don't think this is the cause. Harddrive and/or file system errors could cause this, or improper initiation of an antivirus scan. I asked you to check to confirm a/v scan wasn't enabled in bitcomet, it's in the options, if you can't find it, I'll point you to it.

I might be slow to reply the next few days, My computer is in pieces and I've been using an old dinosaur that can barely open one page at a time.

No i did not enable scan on task finish.

The option to add .bc! and for final hash check have existed for a good long while Yes But

GUI Improved: new setting in advanced option page to enable/disable auto hash check after downloaded file changed NO,this is new from version 1.26

post-59166-13169451070832.png

Edited by blackps (see edit history)

Share this post


Link to post
Share on other sites
No i did not enable scan on task finish.

I didn't ask you if you enabled it, I asked you to check if it was enabled.

Share this post


Link to post
Share on other sites

I see that on your screenshot now, it didn't load the last time I viewed this thread. I've also been trying to reproduce this error and can find no combination of options to make bitcomet crash.

GUI Improved: new setting in advanced option page to enable/disable auto hash check after downloaded file changed

This won't trigger a hash check if bitcomet renames the file, it only hash checks files that have been altered since bitcomet last used them.

ps. could the rest of our staff and beta testers see if this can be reproduced?

Edit: I think I may have just found something here, I'll report back later.

Share this post


Link to post
Share on other sites

Ok, so far I've determined that the task you linked will crash under Windows 7 x64 if you enable "add bc!", "hash check upon complete" and "hash check if file changes".

This problem doesn't seem to exist on Vista x86

Additionally, on my Windows 7 ultimate x64 PC, when bitcomet crashed, windows prompted me that it had to change compatibility settings for bitcomet. After this change rerunning the same task didn't cause it to crash.

On another PC running Windows 7 home premium x64, it crashed with no such prompt about compatibility, and redownloading the task caused a second crash.

Further testing is needed, but I'm going to consider this bug as verified and pass it on to development.

TuuS

Share this post


Link to post
Share on other sites

Local disk,i have a antivirus ( avast 6 ) but i did not set bitcomet to scan task on finish, another problem is that i can't report the crash , see pic.

Thank you for the report, this issue has been forwarded to the dev team.

The development team is working on the crashdown issue at the moment, but we are not able to reproduce the error yet. We will keep trying, once this error is fixed, you will know from the changelog of a future version.

Share this post


Link to post
Share on other sites

Yep, it crashes on XP SP3 32 bit too, both on the beta and on the v.1.29 stable. Except, not exactly every time (one time it didn't).

The crash reporting routine says "Connect fail !" as well (BTW that should be changed into "Connection Failure" or "Connecting Failed").

post-53766-13171567142059.png

Share this post


Link to post
Share on other sites

Just wanted to let you guys know that I am also having this problem since upgrading to version 1.29. I do have both the option to change file extensions enabled as well as the virus check (Microsoft security Essentials) to scan the files after completion. ( I am running Windows 7 ultimate) with 8 gb ram, 600 mb max cache size... I have also noticed that with the new version, even when I have the cache set above the total size of a torrent I am sharing, the cache size is not maxing out and is still creating more disk reads than id like... I do not have a screen shot of this at the moment, but will get one if you think that the cache may be causing the original issues for this post. I just wanted to throw this in because it is the only other thing i have noticed since upgrading....

Thanks a bunch you guys....

I am loving bitcomet (especially the LT Seeding) and will refuse to use any trackers that specifically state not to use Bitcomet.....

Solar.....

Share this post


Link to post
Share on other sites

Thanks solar, if you're inclined to try, see if disabling the bc! file extension stops the crash problem. When testing it's best to use a small torrent and repeat the download several times, this reduces the possibility that other factors are causing the problem.

As for the disc cache, it will keep common bittorrent pieces in ram memory, but bitcomet will still need to access the harddrive for pieces that aren't in ram, and for normal application use. Windows will also use the disc for virtual memory, so you can't stop all disc activity with a big disc cache.

Also, if you're going to run a large disc cache, use bitcomet x64, it doesn't have the memory limitations that 32bit apps have.

Share this post


Link to post
Share on other sites

So far, in fact, the only real reason for the 64-bit app is the ability to use huge cache sizes, at least as far as I can tell.

Share this post


Link to post
Share on other sites

Just an update :

I have disabled the bc! file extensions and it seems to be working, I will continue to test this for a few days and report back .....

thanks a bunch for the help

Solar

Share this post


Link to post
Share on other sites

Yep, it crashes on XP SP3 32 bit too, both on the beta and on the v.1.29 stable. Except, not exactly every time (one time it didn't).

The crash reporting routine says "Connect fail !" as well (BTW that should be changed into "Connection Failure" or "Connecting Failed").

post-53766-13171567142059.png

Dev team leader just told me that the error report server is out of service, and my teammates are trying to fix it asap.

During this period, the error report may not work properly, and users can't see the submit buttiom.

Share this post


Link to post
Share on other sites

I am also experiencing NTDLL.DLL crash everyday, upon file download complete, maybe 30 to 50 times a day.

Currently using

Windows 7 Professional X64 Bitcomet 1.30

Before using the 64-bit version, I experienced the same crash on 32-bit 1.29.

Upgrading to 64-bit did not make a difference at all. It was very disappointing.

*** Please solve the problem involving NTDLL.DLL ***

Share this post


Link to post
Share on other sites

I am also experiencing NTDLL.DLL crash everyday, upon file download complete, maybe 30 to 50 times a day.

Currently using

Windows 7 Professional X64 Bitcomet 1.30

Before using the 64-bit version, I experienced the same crash on 32-bit 1.29.

Upgrading to 64-bit did not make a difference at all. It was very disappointing.

*** Please solve the problem involving NTDLL.DLL ***

Try running it in vista compatibility mode see if it helps.

Share this post


Link to post
Share on other sites

Guys... I upgraded to BitComet 1.34 from 1.33 and i have been having random crashes after random torrent downloads & restarts.. there is no pattern in crashes... I have been using BitComet for nearly 4-5 years... and i have faced occasional crashes(maybe 2-3 in 4 years) but since updating to 1.34 i have had 10-15 crashes in less than a month...& it drives me nuts to wake up in the morning and see my tasks are not downloading anymore...

No iave not selected any anti-virus scanning after download & even in bitcomet options page it is not selected...

Hope to find a fix soon...Now reading this post i have made check_if_filechanged to false & will update you guys....

My SYSTEM CONFIG:

Core2Quad q6600 2.4GHz

Windows 7 32-bit

4GB RAM

Edited by shivsr (see edit history)

Share this post


Link to post
Share on other sites

There are a few optional things that bitcomet will do when a task is complete that aren't required. One is a final hash check, the other is to rename the files to change the file extension from .bc! to whatever the files originally were. I understand why many users like using the .bc! file name option, so you can look at a file and know if it's complete without opening bitcomet, but if you're having this problem and can't track down the cause, I'd suggest turning off this option too and see if it makes a difference then report the results.

It would be best to make one change at a time so any improvement can be linked to a specific change and we can report the findings to development. If you make several changes and your problem is fixed, it will be of no help to millions of other users and we are after all a community that are here to share, so I encourage everyone to help in the process of improving the product.

Good Luck

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...