Exception Thrown


Hello again,
Another bug caused when trying to compress specific directory. The Exception is shown below as requested. I am going to start looking at the cause now as I am unable to send you the content of the directory as it is sensitive data. Tried to reproduce it without the sensitive data but couldn't. I'll see if I can fix it.
Any feedback is welcomed. Thank you.
(It doesn't matter if I use the password or not.)
(Removed Exception an attached as file)

file attachments


TurboPascal wrote Jun 5, 2010 at 11:38 AM

Not very legible with wrapping. Here is a text file of the exception.

wrote Jun 5, 2010 at 11:44 AM

wrote Jun 24, 2010 at 4:06 PM

wrote Jul 14, 2010 at 5:39 PM

interscape wrote Jul 14, 2010 at 5:40 PM

I am also experiencing this bug. I'm going to try stepping through the source to see what exactly is causing the problem.

markhor wrote Jul 16, 2010 at 9:19 AM

So, did anyone figure it out? I can't reproduce the error without the killer data.

wrote Oct 6, 2010 at 10:44 AM

mrblur wrote Oct 8, 2010 at 9:19 AM

Anything new here? My project hit this wall too.
Problem happens only on Windows XP (SP3), on newer archive builds fine.

I'm trying to attach one single .sql file (big one, 90MB) and a directory that contains over 500 images.
Archive is set to be 7z, LZMA 2 with highest compression rate.

mrblur wrote Oct 21, 2010 at 12:39 PM

Going deeper into this problem I have found that there is difference in compression method between archives built with commandline 7zip (7za.exe) and SevenZipSharp library.
For example - 7za using .7z and LZMA2 as method creates archive that is actually "LZMA2 BCJ" where SevenZipSharp creates just LZMA2.
I have also found impossible to specify two compression methods (which is possible with command line tool using -m0= -m1= etc).

But what's more important I have found that neither LZMA and LZMA2 is working with my files, but with PPMD method everything works nicely.

markhor wrote Oct 27, 2010 at 7:33 AM

You can specify any additional filters using SevenZipCompressor.CustomParameters. Something like { "m1", "BCJ" }.

mrblur wrote Oct 27, 2010 at 3:06 PM

markhor: I did, mostly I was getting "Invalid method" or parameter or something like that. But different compression methods isn't the problem here. My question is: Why neither LZMA nor LZMA2 worked with SevenZipSharp, but PPMD did? And second: Why 7za.exe or 7 zip file manager work fine on same 7z.dll ?

wrote Feb 22, 2013 at 1:16 AM

wrote Mar 24 at 8:22 PM