Keeps crashing....

[mdelig00]

Trying to download groups, and Newsbin randomly crashes. Not all the time though. Application hang, real hard to tell what is causing it.


The program NEWSBI~1.EXE version 6.4.1.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel.
Process ID: 2934
Start Time: 01cde4ba6bc3fb03
Termination Time: 4
Application Path: C:\PROGRA~1\Newsbin\NEWSBI~1.EXE
Report Id: 2920c37e-50ae-11e2-b0f2-5404a64b8898

[wyldemusick]

I'm getting periodic crashes too, usually when downloading new headers in a large group -- although at least once it was grabbing posts, but not downloading headers, and down it went. It takes out Dr. Watson when it does that, too, requiring a three-fingered response as everything seems to clog up at that point. Once I kill Dr. Watson however, Newsbin vanishes and things come back to normal.

XP Pro, SP3 here.

[Quade]

Wonder how much RAM it's using at the time? If you run into the 2 GB barrier (for 32 bit XP Systems) and it'll croak. The fact Dr Watson dies too suggests it's a ram issue.

[Quade]

I got a report with an actual file that caused crashing on the IRC channel. Fixed it. The fix will be in 6.42B1.

If it's the same cause, you can stop the crashing by checking "Write Downloaded Files with no memory buffering" in the performance options. Then restart Newsbin.

[Miimario99]

Just upgraded to Version 6.41: 00 4A 8A 23 C9 88 a couple of days ago. I was on 6.21? After the upgrade I've had about 4-5 crashes in the last two days when downloading files and headers.

WinXP Pro, 3GB Mem, Quad CPU. Nothing new but upgrade, I don't remember NB every crashing before with this PC.

I know this is not much help.

[Quade]

Follow my advice? I suggested something to try.

[Miimario99]

It crashed again, so I made your change. I will post an update IF it crashs again, it's seem to mostly occur after several hours of running.

[Quade]

Might want to check how much RAM you're using at the time too. If you do something that hits 2 gigs of ram usage and you're using 32 bit windows, it'll crash. That's a 32 bit windows limit. You'd have to be doing a bunch though. Like loading all of boneless with a couple TB in the download list.

[Miimario99]

New issue, NB "Not Responding", but it did not crash, had to cancel task. NB appeared (cpu use) to keep running even though I could not access it, the screen would not refresh. But before I cancelled the task I captured the performance screen twice, first one at sign of issue, then I shut off my router and captured the screen again.

The post I was downloading when the screen froze successfully completed. I was also dl'ing headers and had a local search window open. It was in this state for a long time and I had done many different searches in the same group, then I went on to something else for a while. The crash and this screen freeze both occur when I have left NB dormant for a while (running without me buggin it).

Image link not allowed for unregistered users

After turning router off below.
Image link not allowed for unregistered users

I don't use NB every day like I did years ago. I'm nearing the end of my 3-day server pass, so NB will soon sit another 15-30 days before I dl again.

My image links do not show, I'm a Registered User but forgot my old user name. So I signed up again with a new name to report this problem, also using a different email. I just tried adding my NB key to my profile but after selecting submit, it returns a screen where the key is blank again. Perhaps because my key is assigned to my old id?

[Quade]

Let me guess you hit the "tab" key from the search text entry. This is a known "hang" issue (not that I expect you to know about it).

It's probably going to take a GUI re-design to make that go away.

[Miimario99]

No, I did not use the tab key at all, not knowingly. The searches were working fine. I had another window open like looking at the dl's folder and maybe a small notepad txt file open. When I returned to the NB window it was not responding.

Thanks for your time.