romanbelkov / xz.net Goto Github PK

In nuget 1.2.2 is the lastest version of XZ.NET.
Is there any reason prevented upload of 2.0.0?

Many improvements like AnyCPU build were achieved in 2.0.0, so it would be better to let developers use lastest version of XZ.NET via nuget.

it's possible?

1. Uncomment "Simple compression (with timing)" part in Examples.cs; rebuild
2. Copy & paste a big file into "XZ.NET\Examples\bin\Debug", rename it to "test.img"
3. Run Examples.exe

Result: test.img.xz is generated, but only 1MB. Try to uncompress it using 7Zip, get Data error

class XZOutputStream has a constant value
private const int MaxThreads = 8;
I think the multi-thread config should be decided by user.
For example, I'm going to write some C# app using xz to archive some log files on a server which has 40 cores -- yes, a very powerful server, so I hope to use 32 threads to do the compression in parallel :)
In case when user has set an irrational number of threads, we can use Trace.TraceWarning to issue a warning message.

XZOutputStream throws an exception when its preset set to 8 or 9.
For detail, this exception is raised from XZOutputStream.cs line 83.

System.InsufficientMemoryException: 'Memory allocation failed'

It only happens if XZ.NET is using 32bit version of liblzma.dll, and it happens regardless of liblzma.dll's version (5.2.1 and 5.2.3 tested).

To reproduce, please use the test code from pull request #8 .

Tested Environment

• Windows 10 x64 v1709
• .Net Framework 4.7.1 installed
• XZ.NET 2.0 trageting .Net Framework 4 Client Profile