newsbin.com

Hi,

in the last days Newsbin crashed about 5 or 6 times after either hitting Ctrl+B or Ctrl+N in the Interset Search results or NZB.
Actually I'm able to reproduce it - anything I can do to give you more information?

Best regards

billy

I'm unable to reproduce this.

Local or I-Search?

i couldnt replicate it either

Quade wrote:I'm unable to reproduce this.

of course, you aren't - it doesn't always happen.
But actually I'm able to reproduce it.

Current situation is:

- I partially downloaded a post (upload still in progress)
- I've started another download
- I've loaded a new NZB for the first download from MysterBin
- I've selected a new part of the first download and hit Ctrl+B and then Newsbin crashes

I'm pretty sure you will not be able to reproduce it even if you're creating the same
situation. But maybe I can turn something like a debug mode on and give you more
information.

I wouldn't have created this thread if this would happen only 1 or 2 times in a month like
with 5.5x (had the same problem there very, very rarely). But with 6 this happens 1 or
2 times a day and it would be nice to find the reason.

Best regards,

billy

There's not a 'something like debug'. If you can try to simplify the process to repro, that would get it solved a hell of a lot faster. Currently you require finding a post currently being uploaded and having(just one? any?) an nzb from a specific source. I seriously doubt the nzb is critical, but you never know. Also, specifically *how* are you stopping downloads? Are you selecting the parent of a compact set and hitting pause? Selecting some of the elements directly? Hitting delete and reloading?

You are also saying it used to happen with v5, so that suggests it's unrelated to the new compact modes. My first guess digging through your description is having multiple entries in the dload queue, one from spools(you didn't answer the question of spools or i-search?) and another from an nzb that represents the same thing are somehow colliding, perhaps with cross-posted who knows. I can't reproduce that, however, with nzb's from nzbmatrix. A better way to deal with this is to have an nzb from wherever you're getting it from, preferably not a massive post, and try to repro with specific steps. Submit this to tech support. A second thought is the currently being uploaded status is screwing things up, in which case I'd argue 'don't do that'. Wait for the upload to finish - obviously you aren't going to get it anyway. That's obviously going to be tricky to reproduce.

DT

I made some further tests e.g. paused the one and only one active download and then tried to
download the new part again or instead of opening the NZB directly from my browser (Firefox)
I've openend the NZB from the Temp-Folder. Sometimes Newsbin crashed after hitting Ctrl+B sometimes
not. Actually it doesn't crash anymore.
I would like to say problem is gone, but I think it isn't - It happened to often in the last days and I think
I just can't reproduce it anymore.

If I'm the only user with this problem, ok, it's my problem. But if there are other users it could be
necessary to find the reason.

What else can I say: 90% of my downloads I'm adding from the Internet Search to my download queue,
for the last 10% I'm creating a NZB at either NZBIndex or other NZB-Site. I do not download Headers.
I always use Ctrl+B or Ctrl+N to add something and I think it already happened in every case:
Internet-Search + Ctrl+B, Internet-Search + Ctrl+N, NZB + Ctrl+B and NZB + Ctrl+N.

I'm pretty sure I will never be able to tell you "do this and do that" to reproduce the problem because
of it's nature but this does not mean there is no bug.

it happened again one minute ago.

- one active download in the queue
- I've executed a search in the Internet Search
- I've added two posts (6 search results: rar, sfv, nfo) to the download queue (Ctrl+B)
- at the time I wanted to add two more posts to the download queue Newsbin crashed

after restart everything was fine.

All we can do is try and reproduce based on description. What you appear to be saying now is that the nzb was a red herring, we now know you're talking about inet search, and the process is nothing more complicated than downloading, searching and adding more files to the queue? It's also unrelated to trying to 'double load' the same posts from different sources, yes? That makes it a lot easier to find.

DT

DThor wrote:and the process is nothing more complicated than downloading, searching and adding more files to the queue?

yes.

DThor wrote:It's also unrelated to trying to 'double load' the same posts from different sources, yes?

yes, because it happens other times as well.

Well, I tried kicking the shit out of this process, worked fine. Added craploads of posts, some with RMB add, some with Ctl-e, some with shift double click, because you're not providing any specifics about exactly how you're doing this(it could, for example, be merely a specific GUI issue and is driven by exactly what you're doing). I searched, added, re-searched, added some more, shifted positions around in the dload queue, it was fine.

To be fair, I'm running an internal beta, it's always possible there was something that was fixed. About all that can be done at this point is note it and keep an eye out for other reports of it. I'm assuming if there's anything relevant like you have 2 TB in the dload queue, you're downloading to a network drive, you're running in a VM etc etc you'll offer that up rather than needing to ask specifically.

DT

exactly I'm doing the following:

1. I search for somehting in the Internet Search
2. I select a post and either hit Ctrl+B or Ctrl+N (always!!!)
3. I select a directory or enter a new one and start the download
4. go back to 1. or 2.

don't know what else you could want to know.

Regarding my configuration the only mentionable thing is that I'm always
downloading to the same encrypted drive.

To wait for other users with the same problem is fine for me.

I'm always
downloading to the same encrypted drive.

That would be one of those thing we would want to know. Given you can apparently repro so easily, can you quickly test to a non-encrypted drive and see if it still happens?

DT

ctrl+b and ctrl+n?

DThor wrote:Given you can apparently repro so easily, can you quickly test to a non-encrypted drive and see if it still happens?

I can't anymore - it was just yesterday for a few times. After I made some test it was gone.
But it still happens one or two times a day. Tomorrow I will test a non-encrypted drive.

richy99 wrote:ctrl+b and ctrl+n?

Ctrl+b = Download to existing directory
Ctrl+n = Download to new directory

billynews wrote:Tomorrow I will test a non-encrypted drive.

unfortunately, I had a crash on the other drive as well.

OK, we'll keep an eye peeled. Certainly I see a fair bit of IO going on, a little more thrashing than I would expect, but no crashing. Again, I'm running a later beta, so possibly it fixed itself.

DT

I didn't think this had anything to do with what drive you use. I suspect some timing issue or that internally something gets corrupt, then the Ctrl-B simply triggers a crash in an already damaged Newsbin.