Still crashing, 7.0 Final

[JMark]

Update headers from multiple larger newsgroups in succession still locks up like it always has. Even and update . close NL > reopen NL update next group of groups locks it up.

No crash reports available because forced to use Task Manager to close NL. Then reopen to restart update. If the Queue had completed DLs prior to crash, they start anew.

Same issue for years now.

[Jed]

Header retrieval has always been a disaster. I just get the headers in a very few groups and then shut down NL so that I don't lose everything when it crashes.

[JMark]

Hey! Caught one...

Bug ID:
jdsoijs

Bug Data #2:
Access violation at address 00406C4B in module 'newsLeecher.exe'. Read of address 474D30D5

[JMark]

Attempting to do an all group clean crashed it again. Clearly, NL is incapable of updating or maintaining multiple groups which contain large numbers of headers.

[JMark]

Bug ID:
gZip avail in > 0

Bug Data #1:
3

Bug Data #2:
[na]

[JMark]

Continual now on group update

Bug ID:
gZip avail in > 0

Bug Data #1:
3

Bug Data #2:
[na]

[JMark]

Bug ID:
oxzolydso

Bug Data #2:
Access violation at address 00C9BDB0 in module 'newsLeecher.exe'. Read of address 3DB3C3C0

[Barking Spider]

I too have been having trouble with getting groups. Here is an attahed

NewsLeecher_v7_Capture.JPG (237.91 KiB) Viewed 13118 times

screen shot of when it crashed.

[Barking Spider]

Forgot to mention, Windows 10 x64 with 8gb ram. Also in the picture, there are only the three groups defined for this testing.

[slobster]

I know this is not a fix, but only having one bot to do this results in no lockup.

Set up a separate server just for header collection and limit to one bot

[kaspkp11]

Bug received as follows: -

17:52:52 --------------------------------------------------------------------------------
17:52:52 Bug Occurred - Line #1: vhioltbnh
17:52:52 Bug Occurred - Line #2:
17:52:52 Bug Occurred - Line #3: data error
17:52:52 --------------------------------------------------------------------------------
17:52:52 vhioltbnh


Windows 10 virtual on MacBook pro. Restart has no effect.

[desslock]

Try disabling compatibility mode for newsleecher.exe. This reduced the number of crashes on group updates on Win10 for me. That along with reducing download speed when doing group updates to avoid crashes due to cpu/memory/disk bottlenecks... running on a VM here.

[nambit]

It's really crashing badly all of a sudden. I have unistalled newsleecher and deleted all files in my user folder, but it still crashes.
First I get an access violation error, then later on it says out of memory.

I am running Windows 10 64bit with 16GB of memory. HELP!!! I am unable to use this program.

Thanks,

Edit: Luckily I have found v5.0 final and it seems to be a temporary fix, but now there are lots of errors downloading for some reason. At least it works but really, there has to be a fix for this!

Here's a shot of a recent error on v7 final before I gave up.

NL BUG.JPG (56.25 KiB) Viewed 9891 times

[JMark]

Update Groups, no headers in DL Queue, no headers in Extract

Bug ID:
14p09y10o

Bug Data #2:
Access violation at address 007DE447 in module 'newsLeecher.exe'. Read of address 7B48F1C8

[scuba]

I will talk to the development team about it.
Thanks,