Segment size reporting bug

[Rigor O'Mortis 1]

Image describes the bug:

ApexDC 1.0.1 running on Vista SP1 64-bit, AMD Phenom quad-core CPU on AMD790X chipset.

[Satan 1]

Sorry, i'm clearly missing something, what is wrong?

[Rigor O'Mortis 1]

Segment size shown in column: 501.39 KB

Already downloaded shown in progress bar: 1.37 MB

Real segment size: ~2MB

It's reporting 500KB on a 2MB segment. The progress bar was full when download reached 500KB, but the percentage shown on it was only 25%.

[Satan 1]

Not a bug, it's meant to do this. It overlaps on segments when a user is faster. Or, in the scenario where you have no other users to dl from.

[Rigor O'Mortis 1]

It seemed to me that Apex knew from the beginning that it will overlap. It would be nice to change and actually show the real size that it is downloading, even if it is overlapping.

[Zlobomir 3]

It seemed to me that Apex knew from the beginning that it will overlap. It would be nice to change and actually show the real size that it is downloading, even if it is overlapping.

How could Apex know it, esp. when faster user can appear at any time?

[Big Muscle 1]

This has nothing to do with overlapping. It's a bug.

[Satan 1]

SDC's or Apex's?

[Big Muscle 1]

I don't know but have never seen it in StrongDC++.

[Crise 26]

I don't know but have never seen it in StrongDC++.

I don't know for sure either, but not long ago I checked the transferview and queue & downloadmanager code of apex against SDC and at least I can't see any changes from apex that would affect segment size reporting in any way.

[Big Muscle 1]

I think I know where the bug is... the "bad" size comes from TTH tree which was downloaded just before this segment. The size won't be updated then in some cases (especially when there's very little sources at the beginning)