PA eats all the memory & cancel button doesn't work

[Ihmemies]

Why powerarchiver uses all available memory when extracting files? I use current folder as “temp” selected (since I hate temp folders). It takes ages to unzip anything if the program first unzips to some random folder in C:\ and then moves the files… (supposing I even have enough room for it)

http://hakkarainen.kuvat.fi/kuvat/2008/random/pa_2007.png/full

The memory usage grows till it’s 95%, then extraction stalls and everything becomes very slow when Windows is out of memory.

Also cancel button has been buggy for as long as I can remember. It won’t cancel the extraction until the current file has been extracted. If I want for some reason to cancel, I need to kill the program from task manager if I want to stop it extracting today

[spwolf]

how much actual memory is PA using when you look at processes? For ZIP it should not be that much at all.

[Serhiy]

this happens when you extract a large file from zip archive. and it takes as much memory as the size of currently-extracted part of that file. (if the compressed file size is 1 gb and the extraction process is on 50%, it will take 0,5 gb of RAM). But it is not taken by POWERARC.EXE process. and I don’t see in the task manager what process is using it.

[spwolf]

it seems Vista is caching it, but I dont understand why is then system running out of RAM if it is automatic Vista thing.

are you also using x64 version of Vista or 32bit?

[Ihmemies]

@spwolf:

it seems Vista is caching it, but I dont understand why is then system running out of RAM if it is automatic Vista thing.

are you also using x64 version of Vista or 32bit?

I’m using 64-bit version of Vista Home Premium.

The zip I was extracting is 8,22GB. It has several 640MB files inside. So this is Vista’s fault, rather than PA’s, nice to know :p Altough I can’t understand why it’s doing whatever it’s doing…

[spwolf]

@Ihmemies:

I’m using 64-bit version of Vista Home Premium.

The zip I was extracting is 8,22GB. It has several 640MB files inside. So this is Vista’s fault, rather than PA’s, nice to know :p Altough I can’t understand why it’s doing whatever it’s doing…

there are some current kernel leaks in Vista that are not fixed in SP1. I tried one of the manual fixes and it does not solve this problem.

We are looking if we can do something differently so it does not happen.

Cancel issue will be fixed in future major update for sure (not sure if we are going to have any minor updates).

thanks