Helicon Soft Forum

Anyone else having catistrophic probems with version 5.1.5 after years of no problems with earlier versions? The program hangs when I press the new stack button so hard the End Task in Task Manager takes about 5 minutes to terminate the program. I also have an error message every time I save to tiff...access violation at address 00a687E6 in module PolyImagePro.dll Read of address 00000004.

Its not nice to have this EveryTime I want to process a new stack.

We cannot reproduce it so far. Please upload to our server one of your images (as described at http://www.heliconsoft.com/ftp.html). Please also try to do the same with demo images and check if the same problem appear.

Yes, I too have nothing but failure with new version.


How can I go back?

Here is the link to the previous version:
http://www.heliconsoft.com/downloads/He ... s5.1.2.exe

I spoke to soon:

I removed, then redownloaded. The second time I left out the beta remote.

It works fine now.

Rique

I have the same problem with version 5.1.9 x64.

Each time I save a TIF file, i get "Access violation at address 00C987E6 in module 'PolyImagePro.dll". Read of address 00000004"
The good thing is the result image is save correctly despite of the message. But the bad news is HF UI is locked up, and you have to kill it with task manager and relaunch it.

Size of the output TIFF image is : 5616x3744 (8b)

Another issue (I don't know if it is related), if that my stack of images (16b TIFFs) leads to a 8b result !


g0b

We cannot reproduce this error so far. Which OS do you have? Does it happen with both methods A and B? Please disable processing server int the preferences and try if this help. Please upload one of the images to our ftp server as described at http://www.heliconsoft.com/ftp.html

Hi,

I've uploaded a few image of the stack on the ftp (the full stack is too big, and anyway a few elements are enough to reproduce the bug).
With 5.1.9 , saving the result in TIFF crashes the app (and the stack is incorrectly computed in 8b). With 5.1.2 saving in TIFF is ok, but the stack is also computed in 8b instead of 16
It occurs both with method A and B.
My OS is Win7 x64

Thanks for your help !

Regards,
g0b

Thanks for the files. We were able to reproduce the bug when 8 bit result was saved from 16 bit source images. But not the crash. This bug appears only with your images, I suspect that happens because they are gray. We will fix this in the next version.

OK, thanks a lot for your help !

When do you plan to release a new version with those issues fixed ?

Regards,
g0b

We are preparing new version. It will be published next week.

Excellent ! Thanks for your efficiency !

g0b