Download queue stalls after a few mins

[MVer]

Dropped this in the wrong place, sorry for that.
Anyway, not a 6.50b14 issue as I was on 6.50b13 when it started.

On holiday for 3 weeks, shut down, came back, started up, dropped some stuff in the queue, dloads started as normal (6MBits as always), minimised, then on checking later (some mins), the downloads have stopped.
No high cpu loads, nothing odd in the logging, no nothing. Installed b14 (just in case), same issue. Tried all the config options (mentioned in other posts on stalling), nothing seems to have an impact, simply after a few mins, it just winds down and stops.
Nothing wrong with the network, other downloads on the same machine maintain 6mbits without trouble. The Syno NAS can do the same.
Been running most of the betas for many years without major trouble and I never saw anything like this before.
Can anyone tell me where I might start to look for this, logging etc etc.

I can lengthen the time it keeps going between minutes and an hour or two by only adding one or two items at a time (a.b.teevee) but inevitably, it stops. Left 6 in the queue this AM, returned from work, last item was about 15% dloaded and stopped again, Restarted, going strong - but likely will stop again.

Watching the cache, starts at 200/200, goes down to 40/200, then jumps back to 160/200 (sometimes 170/200). Is it a chunk cache issue, could/should I define more ?

Any ideas would be gratefully received, Many thanks...

[Quade]

Puzzler. I'll have to think about it. Tell me about the PC and the operating system.

What do you see in the logging tab?

[MVer]

Tnx. It's Win 7 x64 Ult. 16GB ram, AMD hex core (1100T). Boot is 120GB OCZ Vertex3 (symlinks to move caches and transient data to 3TB Internal. NBPro chunks and re-assembly (par's extract etc) are on different spindles.

Logging, it just goes to sleep and won't wake up again (which is possibly the crux of it):
[07:32:10] DEBUG FileTracker Clear:
[07:32:10] DEBUG FileTracker Clear:
[07:33:28] DEBUG Download: Idle Connection Closed:Giganews
[07:33:30] DEBUG Download: Idle Connection Closed:Giganews
[07:33:32] DEBUG Download: Idle Connection Closed:Giganews
[07:33:33] DEBUG Download: Idle Connection Closed:Giganews
[07:33:36] DEBUG Download: Idle Connection Closed:Giganews
[07:33:41] DEBUG Download: Idle Connection Closed:Giganews
[07:33:41] DEBUG Download: Idle Connection Closed:Giganews
[07:33:42] DEBUG Download: Idle Connection Closed:Giganews
[07:33:43] DEBUG Download: Idle Connection Closed:Giganews
[07:33:43] DEBUG Download: Idle Connection Closed:Giganews
[07:33:44] DEBUG Download: Idle Connection Closed:Giganews
[07:33:45] DEBUG Download: Idle Connection Closed:Giganews
[07:33:45] DEBUG Download: Idle Connection Closed:Giganews
[07:33:47] DEBUG Download: Idle Connection Closed:Giganews
[07:33:48] DEBUG Download: Idle Connection Closed:Giganews
[07:33:49] DEBUG Download: Idle Connection Closed:Giganews
[07:33:51] DEBUG Download: Idle Connection Closed:Giganews
[07:33:55] DEBUG Download: Idle Connection Closed:Giganews
[07:33:56] DEBUG Download: Idle Connection Closed:Giganews
[07:33:56] DEBUG Download: Idle Connection Closed:Giganews
[14:19:31] ERROR Resolver: Unable to find Download data - 1
[35 identical lines snipped]
[14:21:16] ERROR Resolver: Unable to find Download data - 1

I found it had finished at 14:19, so dropped a few more in the queue but it refused to start downloading and I had to restart it (and add the posts back again).
Wonder if that helps any?
Tnx...

[Quade]

Do you have another PC to test it on? Maybe an intel based one? The only thing that stands out is the AMD CPU. Maybe there's some timing bug in Newsbin that only happens with AMD. Do you have it set to pause download while unraring? It's almost like internally it's paused.

[MVer]

Tnx.
No pause on unrar (all unchecked in Perf options).
Spotted a Resolver message in the debug pane:
[08:34:03] HIGH Open Post - Giganews ARTICLE <1376281620.32203.1@eu.news.astraweb.com>
| 220 0 <1376281620.32203.1@eu.news.astraweb.com>
[08:34:03] DEBUG AutoPAR: ScanFile Blocks:33 File is Perfect: jungle.gold.s02e01.720p.hdtv.x264-killers.r04
[08:34:03] DEBUG AutoPAR: Scan 33 Blocks File: jungle.gold.s02e01.720p.hdtv.x264-killers.r04
[08:34:03] ERROR Resolver: Unable to find Download data - 1
[08:34:03] ERROR Resolver: Unable to find Download data - 1

<Don't post what you're downloading>

[08:35:00] DEBUG Download: Idle Connection Closed:Giganews
[08:35:03] DEBUG Download: Idle Connection Closed:Giganews

This must be PC related but scratching my head to see what.
Could run it up on the Mac (inside a parallels Win-7 x64 VM) at the weekend, I expect that will prove it's my PC of course Image link not allowed for unregistered users as I am even more convinced it's the computer not nbpro.

Can you tell me what data / store the resolver message refers to? I can dig deeper into that this evening (as in move the data store it's referring to, to another spindle to eliminate an HD issues).

Many thanks so far...

[Quade]

I'm just throwing the AMD idea out there. I'm not actually blaming the PC so much as a timing problem in my code that's simply happens with AMD. It would still be a bug.

It seems to happen after a successful unrar which is sort of odd.

[MVer]

Tnx, understood.
I'll try it in a VM as I said and see if I can lay my hands on an Intel PC/laptop/something to test more. I wouldn't have anticipated it being the AMD as it's run so stable for me for years on AMD's and the thing is on 24/7 and usually doesn't (need to) get rebooted for weeks, a tribute to npbro too as one of the busiest apps running. It's run for almost 2yrs in this config and never glitched. So after a 3wk shutdown, then to do this on power up now, really makes me think PC related rather than nbpro.

One thing I did after my previous reply was to disable the AutoPAR function and it hasn't stopped since. Connection speeds flutter up down quite a lot (between 6mb and down as low as 50kb (during unrar) but it doesn't stop. I was thinking to move the data stores to clean HD's (got a couple of 1.5TBs I can slot in and reformat, as it seems to be a bit stretched around the unrar (pocess of elimination really).

I could go back to b13 (or earlier) over the weekend but was on b13 when it started, so I assumed that wouldn't probably help.

[MVer]

Hi Quade,

Sorry for the delay, just too too busy to get enough time to do much.

nb worked fine in other tests systems, same config (slight changes to suit local HD paths). Finally did an extensive set of win updates (60 something) and after a several reboots, the problem has just gone away, so I can't explain it but it seems to have been OS, certainly not nb. Is it useful to you to know the updates that got applied?

Many Thanks again and sorry for any false alarms.

[Quade]

I don't consider it a false alarm. I need to figure out what's up with AMD and my code. I think it sounds like internal messages between parts of Newsbin are being lost so, it doesn't know what to do next and stalls.