Crash when downloading certain postings!

[Frasier]

Hi!

AltBinz fails to download several postings. For example:

Group: a.b.etc.
Header: Planet Wissen Teil 3 by Antichrist&Archie Medes - "Planet Wissen Teil 3 Mathematik Die Zauberwelt der Zahlen by Antichrist&Archie Medes.par2" yEnc

There are 15 postings all with "Planet Wissen" at the beginning and AltBinz can hardly download any of them. It seems to download something and then crashes horribly at the decoding phase. Vista reports that AltBinz has stopped working and then runtime errors pop up every second...

I've encountered this before with other postings, but I blamed the postings. Now it's clear that AltBinz seems to have a problem.

I'm using v0.28.1 under VIsta x64.

Regards!

[Hecks]

So what you're saying is: Alt.Binz has a problem with those posts rather than Alt.Binz has a problem in general.  I guess they're more examples of bad yEnc encoding.  Confirmed with another newsreader?  Maybe someone else will be bothered enough to try the same posts to test.

[Jesus]

I can't find anything terribly unusual about the post.

It was posted with the most common program, YENC-POWER-POST-A&A-v11b

The filenames are kind of long and contain an ampersand; maybe a filename string with '&A' in it triggers some bug.

The 15 parts were posted to 15 different newsgroups; if you loaded a single NZB then alt.binz will download the post from 15 different newsgroups.  That makes the post a little unusual.

Gave me no trouble.  I loaded a NZB into Xnews and downloaded 3 files, which show green in QuickPar.  I don't have alt.binz

[Hecks]

@ Jesus

You don't have Alt.Binz?

Edit: Well, I tried the Teil 3 example given by the OP, and it downloaded an unrared fine here when the subject wasn't used as the NZB name (with dl folder named after NZB).  When it was, decoding failed, CPU and memory went wobbly, and my log was swamped with error messages:

[Dec] Exception Cannot create file "". The filename or extension is too long

Alt.Binz could deal with such situations more gracefully, but the general solution is simple: use short/safe NZB names, and always read your Log before posting bug reports here.