newsbin.com

Hi Guys

NB6.42 Build 2146

For a while now if I close a tab too quickly after deleting whatever posts are in it NB crashes.

To get round it I now delete the posts in one tab and then open up the tab for the next group or GOG to look at the posts in it and decide what I want to do with them - download or delete. The post count in the previous tab does not reset to zero after I had deleted all the posts - but if delete all the posts in the second tab, the post count in the first tab goes to zero. This occurs no matter which group tab I open so its not specific to any certain group/GOG but occurs with all of them.

eg
open TV group tab - 200 posts - delete all - post count stays at 200.
open mp3 group tab - 300 posts - delete all - post count stays at 300 but TV group tab count goes to zero and so on.

Just though I would point it out in case it has any significance on NB crashing.

Trying like hell to repro with a new, internal cut and it's not happening. Not a guarantee of a fix, but hope.

DT

When I said it has been happening for a while, I got curious and went back through my 'post' history. I mentioned it back in April 2011 - didn't think it was that long ago.

Since then I've upgraded my PC with a new MB and Processor and also upgraded my OS to a 64 bit system. The only thing that's stayed constant is my NB configuration and spool files - could there be something in them that causes it?

It's certainly possible it's related to the spool files, but if it's *all* of them, not likely. I would wipe and redownload one GOG perhaps and see if it ever gives you grief.

DT

This sounds very similar to what has been happening to me for several releases. I open about 14 GOG as fast as possible and then start reading and closing them. If I do it too quickly (assume some are still loading) NB will occasionally crash. Can't exactly reproduce on demand, but have found that if I give it enough time to load all the GOG's completely, it doesn't happen. I have lived with it since I have found a solution for me. Should have reported it earlier. When it crashes not all the GOG's are marked read and I can reload some of them again. I am using NB 6.42 B2148 and I only have 2 weeks of data in the spool files.