Newsbin 6.91 RC3 - Build 5855

[Vimes]

Mine was a full reinstall from removing everything from the previous build.

I do still get the random...

Faulting application name: newsbinpro64.exe, version: 6.9.1.9, time stamp: 0x66e47509
Faulting module name: explorerframe.dll, version: 10.0.26100.2894, time stamp: 0x7d07b96a
Exception code: 0xc0000005
Fault offset: 0x000000000007ac3b
Faulting process id: 0x3E58
Faulting application start time: 0x1DB6F714387DBB7
Faulting application path: H:\Newsbin\newsbinpro64.exe
Faulting module path: C:\WINDOWS\system32\explorerframe.dll
Report Id: 376abf70-0756-43ee-9621-e5bf6ba2b7df
Faulting package full name:
Faulting package-relative application ID:

It will always occur at the time of completing an extraction. The extraction is done successfully.
Starting NB back up and the file(s) restart to download as though they haven't done previously.

Nothing has changed really.
StartAllBack is being used.

as well as the failed file list building up, for no apparent reason. I had sent you a mail showing that.

[JayPea]

Mine was a fresh install/second instance to another SSD. Still the same

It's identical to how I initially descibed it to you via PM last year - I'm a StartAllBack user. Pretty much as above from @Vimes

I've just discovered another weird issue: some .epub files won't download. No errors. Nothing. They just dump to Failed Files and that's it. Nothing in logs. I'll poke around later to see if I can raise the level of logging. This is from a group of groups and it's not from a NZB. It's content that I'm finding after refreshing a GoG, actual group being a.b.epub.

[Quade]

I'm giving it another once over. I want you to try a pre-release version so see if the changes fixed it before I try to release it.

I'm not sure why the faulting DLL is even being pulled in. It's not something I'm using. There must be come other windows feature that's pulling it in.

[JayPea]

Happy to test whatever you'd like. Can drop to IRC if easier. However/whenever etc. I would imagine @Vimes would also be interested seeing as he's suffering a similar CTD? More feedback, the better.

I've changed my logging to Verbose to see if I can give you more information about the .epub files attempting to download & immediately failing but there's still nothing being wrriten to the Logging tab. I noticed there was another level lower (Debug) so I'll give it another go with that and let you know.

Cheers.

Update: can see errors like this for each of the failed *.epub files. New encoding or something? :

"[02/13 16:56:32] DEBUG Chunk #1 Filename not found: Re: REQ: pls: [ xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ] TIA - xxxxxx, xxxx - xxxxxxx xxxxx 00 - x xxxx xxxxxxxxxxx - xxx xxxxxxx of xxxxxxx xxxxx (Retail).epub"
&
"[02/13 16:56:32] DEBUG HFC: No Filename in first chunk error: Re: REQ: pls: [ xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ] TIA - xxxxxx, xxxx - xxxxxxx xxxxx 00 - x xxxx xxxxxxxxxxx - xxx xxxxxxx of xxxxxxx xxxxx (Retail).epub"

[Quade]

Here's one to try

https://s3.dualstack.us-east-1.amazonaw ... T-5935.exe

If you still get crashing. Exit Newsbin. Then add this to the NBI file. It will disable taskbar integration.

Code: Select all

[SETTINGS]
EnableTaskbar= 0


Like the pause icon and the progress bar in the taskbar. I suspect the crashing it's taskbar related but I'm not sure. The odd dll's it's crashing in suggests it's something outside of Newsbin.

This one isn't totally untested, I use it every day but I haven't confirmed everything, like Sonarr integration. It should work but, I don't trust anything I haven't tested immediately.

PM me a specific example again of the epub thing. I believe the last time I looked at this, the files were simply posted wrong.

Edit. I remember they're posted wrong. I saw some just now. They put the file counter on the end and not before the filename. I think i remember suggesting you contact the poster and ask them to move the file counter to before the filename,

[JayPea]

Many thanks indeed. Will give it a whirl + noted for both potential .nbi addition and the failing files.

Feedback to follow...

[Vimes]

Thanks. I am testing. Any issues might take a little while due to the inconsistent nature of the issue(s).

[Vimes]

This is with a few nzb's lined up to download and then returning to find....

Faulting application name: NewsbinPro64.exe, version: 6.9.1.9, time stamp: 0x67af9d91
Faulting module name: explorerframe.dll, version: 10.0.26100.3037, time stamp: 0xa068ed4a
Exception code: 0xc0000005
Fault offset: 0x000000000007f0eb
Faulting process id: 0x3350
Faulting application start time: 0x1DB7FA9915B5292
Faulting application path: H:\Newsbin\NewsbinPro64.exe
Faulting module path: C:\WINDOWS\system32\explorerframe.dll
Report Id: 4ff60fa1-fc1c-4874-b2fb-3b1bc4426525
Faulting package full name:
Faulting package-relative application ID:

I will try and add that line now, to the Newsbin.nbi file.

The above is with the test build you posted.

oh, the failed file list continues to build up, as mentioned a number of times. Not related to the files failing.

[Quade]

If Newsbin can't confirm the download with PAR files, they'll get listed as failed. I suspect that's what you're seeing.

[Vimes]

If Newsbin can't confirm the download with PAR files, they'll get listed as failed. I suspect that's what you're seeing.

Point taken. However, with the way certain files are these days, needing these builds of NB, that will mean a large number of them are now shown as being failed files. In fact, for me, each time I download, and they are extracted, it is now a fail. I used to rely on the failed section to be informative and as a warning of something gone wrong. Not it is somewhat pointless due to what is occurring.

Thanks.

[Vimes]

Even with the line added.......

Faulting application name: newsbinpro64.exe, version: 6.9.1.9, time stamp: 0x67af9d91
Faulting module name: explorerframe.dll, version: 10.0.26100.3037, time stamp: 0xa068ed4a
Exception code: 0xc0000005
Fault offset: 0x000000000007f0eb
Faulting process id: 0x5630
Faulting application start time: 0x1DB817903BDE742
Faulting application path: H:\Newsbin\newsbinpro64.exe
Faulting module path: C:\WINDOWS\system32\explorerframe.dll
Report Id: 2f83fd96-dbff-4b0c-9ee6-ab1fef89d362
Faulting package full name:
Faulting package-relative application ID:

that was after having 11 NZB's lined up, it seemed to fail after the 8th was extracted and ctd.

[_DonB_]

One minor modification. The link from Help / "Discussion/Help Forum" is linking to "http://forums.newsbin.com/". The address should be changed to "https://forums.newsbin.com/"

[Quade]

The crashing is happening outside of Newsbin proper. It's not really something I can trouble shoot because it's not happening in any code I control. I'm going to try to see what loads up that DLL into Newsbin. It's not something I manually load or link to. Some other component is pulling it in.

Edit: Maybe recheck that the disable stuff is still in the NBI. I notice when I disable taskbar integration, that DLL is no longer loaded into Newsbin.

[Vimes]

The crashing is happening outside of Newsbin proper. It's not really something I can trouble shoot because it's not happening in any code I control. I'm going to try to see what loads up that DLL into Newsbin. It's not something I manually load or link to. Some other component is pulling it in.

Edit: Maybe recheck that the disable stuff is still in the NBI. I notice when I disable taskbar integration, that DLL is no longer loaded into Newsbin.

Thanks, very much appreciate your help.

For some reason the settings options had not persisted within the nbi file, not sure why that should happen..?

Ok, I think that the setting line to that file might be sticking, it seemed to be getting rewritten each time and that particular line deleted. It seems to be keeping it here now, so I'll continue to monitor and check that line is still there if the fault occurs again.

[JayPea]

For some reason the settings options had not persisted within the nbi file, not sure why that should happen..?

My only suggestion to the 'why' is that perhaps you had NBP open whilst editing or the process was otherwise still locked when editing? That's the only reason I can think of. I upgraded and added my entry without issue. The app has been stable ever since.

[Vimes]

For some reason the settings options had not persisted within the nbi file, not sure why that should happen..?

My only suggestion to the 'why' is that perhaps you had NBP open whilst editing or the process was otherwise still locked when editing? That's the only reason I can think of. I upgraded and added my entry without issue. The app has been stable ever since.

Yes, I did have NB open as I used it to open my data folder whilst making those changes. I was not aware at the time that by doing so it would then revert those changes when closed.

It was only later when testing out what could have happened that I noted the above pattern.

Thanks.

[Quade]

I looked at my post and I didn't mention Newsbin has to be exited to edit the NBI by hand but that is the case. Any manual changes to the NBI while it's open get overwritten on exit.

[Vimes]

Yes, I was not aware of that. It just seemed useful at the time when NB was open to make that open the data folder and edit from there.

Ok, very early days as yet. Lined up a number of nzb files and it seemed to work fine, that is with adding that line to the file, as noted.
Still needs to be tested due to the inconsistent nature, at times, of the issue reported.