This is a discussion on 0.55 stable is out within the BitComet Technical Support forums, part of the BitComet - www.BitComet.com category; Originally Posted by windy rnysmile wrote: windy wrote: [quote:5eb74] Somehow the "allocate before download" feature is still not working. Does ...
But when I go and check at the directory, it says 0 bytes.Originally Posted by windy
Off topic: BTW, someone should change the link to this forum at bitcomet.com. It's still the old link.[/quote:5eb74]
oh, I remembered, it does all the allocation when first piece of data comes. mmmm... seems a small bug to be fix. ^_^
I did a search of the post, but didn't find. Did you still remember where is the post?Ah, my apologies; I fixed my post to correct that. I'll take a look at your post later to see if there's something I can suggest.hello keen, I havent figured out the problem, and I've already posted a topic about my problem, but appears that rnysmile dont want to say something about it...FYI (I saw that you figured the problem out), providing more information than this makes bug reports actually useful.
I have the same problem I believe. I also posted in another thread about it, citing that on the same machine, same torrent, same port (bittornado, my other client, uses a range of ports, but the one botcomet port is in that range), my download rate with bitcomet is never greater than 15, while bittornado gets about 200. I think you are on to one of the problems, limited truely connected peers. As a matter of fact take a closer look, I suspect most of the ones it shows as connected show up as 'local'. Not really sure what 'local' means in that context, but it doesn't sound good.hello keen, I havent figured out the problem, and I've already posted a topic about my problem, but appears that rnysmile dont want to say something about it...FYI (I saw that you figured the problem out), providing more information than this makes bug reports actually useful.
Bottom line is there are significant 'core' issues remaining that make this client 100% unusable for me. I sure hope they get fixed and/or this client goes open source so I can help track down the problem because I sure love its GUI. It may be unusable for me now but believe me, I will keep watching and hoping.
-CodeMonkey
I used to take life with a grain of salt.
Now I take it with 50mg of Valium.
I encountered the following in the 0515 version.
I have a torrent downloading at the bottom of the files list and a few other jobs queueing above the downloading current.
When that torrent finished downloading, the new torrent that started was not the torrent quueing at the top most. Instead the lowest torrent, T1 (the one queueing nearest the newly finished torrent) started first.
I did an experiment and stop T1. The torrent just above T1 started off instead of the top most torrent.
Please fix this so that all new jobs will starts from the top most queueing jobs.
Thanks.
thanks. the queue issue will be fixed~
0517 is a little bit more stable for me... did not get a crash yet... but, all my downloads show up in "seed only" even they are still downloading...
a little cosmetic problem... without this problem, bitcomet is perfect for me!
fixed in 0518 thanks...
0517 is a little bit more stable for me... did not get a crash yet... but, all my downloads show up in "seed only" even they are still downloading...
a little cosmetic problem... without this problem, bitcomet is perfect for me!
Another something that I just remember:
BC can't seem to be able to remember the customized column size that I set. If I remember correctly, BC used to be able to do this.
Anyone got the same problem as me?
with the latest beta version, I do not have this problem... column size are saved correctly for me
zadigre wrote:[/quote:90d87]with the latest beta version, I do not have this problem... column size are saved correctly for me
windy wrote:
[quote:90d87]Another something that I just remember:
BC can't seem to be able to remember the customized column size that I set. If I remember correctly, BC used to be able to do this.
Anyone got the same problem as me?
Just checked. It happened to me every time I install a new version of BC.
BitComet just crashed on me.
What happened:
I was replying the previous message. Then suddenly one pop up window appeared and told me that BC has just crashed.
I restarted the BC and found that one torrent that I was downloading half way suddenly become 100%.
So I started to do manual hashing for that torrent. Usually when I do manual hashing I tried not to do other tasks but since that torrent is kind of big, I started another torrent.
Then the crashing pop up appeared again. Sigh...
I started BC again. Then let the torrent to do the manual hashing without running any other tasks.
Luckily the torrent returned to its actual state of download.
Hope this will help to figure out what happened.
Anyway, just found out that BC got this "report the error" kind of feature.
So, if wanna send the report, just send the [0518]BitCometCrash.zip is it?
The 0.52 (051sends wrong data to the Tracker. This shows itself, when i seed and still have downloaded KB without really having downloaded them. This also happens with the upload where some KB where uploaded in the stats without leeching Clients, but only seeding ones. These KB are only caused by communicating with the other seeding clients but are counted to the transfered Data.
This leads to wrong stats at the trackers.
In 0.52 stable this does not happen.
Just after I posted my previous post, I restarted my comp and it gave me such a fright. It didn't give me any response. I really thought my hard disk was burnt.
After around 5 hrs here I'm back again
The problem now is that every time I tried to start BC. It crashes, even if I go back to the 0517 version.
Any advice?
OK. Did a clean install and manage to get BC up and running again.
Not yet go to manual hash old torrents yet (crossing my fingers and praying)
Here are two possible hypothesises of what happened:
Hypothesis No. 1:
I got a torrent running before. I stuck at 99% and was uploading to some peers who are less than 99%. So I'm not downloading anything even though my status is downloading. Occasionally there'll be some stuff downloaded.
Not very sure what they are and they are very small sized. Eg. I only got a few KB downloads when I have uploaded a few MB. My assumptions would be they are the torrent info that BC needs.
However the time spent downloaded and uploaded are at 99:99:99. I'm not very sure how long I have the torrent running. Could be days (definitely) so I'm not very sure whether the overflow of the time caused this problem or that's what some of you said the 99:99:99 bug.
Hypothesis No. 2:
BC crashed (with the crashed window popping up) after I tried to start a second job. I'm not very sure either whether it is caused by this particular torrent. Since I deleted the previous BC folder, I can't verify.
After I re-installed BC, I went to check my halfway downloaded folder for resumes. The problem is I can't find the folder for this particular torrent. The size of the folder (for 100% download) is around 600MB+.
But then again the folder might not got the chance to be created before BC crashed. And since I enabled "allocate before download" I'm not very sure whether the allocating process caused this (not likely though).
I don't dare to try to download this again so I might never know for sure.
I checked the error log that I've saved. It said "BitComet caused an Access Violation (0xc0000005)". Not very sure what this means though.
Could also be caused by stack overflow coz the stacks become all rubbish characters halfway through.
Need to ask rnysmile something, is it enough to mail just the BitCometCrash.zip? Coz there are also some files like [0518]BitCometCrash.zip.0009. Should I mail those too?
Going to try to do the manual hashing for the other torrent that I was downloading halfway through. If no news from me soon then you'll know something unexpected has happened again.
Edit:
Better don't start another new post.
Just found out that the 0520 is out. What should I do?
Anyway, I managed to manual hash the torrent I mentioned above (let's just referred it as T1 if needed). Managed to hash it successfully to its supposed status.
Now downloading T1 and another new torrent simultaneously. So far no problems yet. (crossing fingers)
I think I better stick to 0517 before I know more of exactly what happened.
It may be a bug in 0.52 520...
I cannot see the upload speed to each peer.
Thank you!
TC
Posting Permissions 
LinkBack URL
About LinkBacks
Reply With Quote
Bookmarks