Good afternoon! First of all, thank you SO MUCH for FileOptimizer! It has been SO useful!
So here we go. I've just downloaded the latest version of FO (8.30.1456).
I'm on Windows 7 pro, 64 bits, french. I'm using the x64 version of FO.
12 GB of ram. AMD 6 core processor. Rock solid system.
I am compressing HD-size PNGs : 1920x1080x24 bits. Uncompressed, these files are about 6mb.
Every time I compress a PNG, Windows throws me an error message, claiming ECT has crashed.
Here's what Windows has to say :
Source : Application Error
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Nom de l’application défaillante ECT.exe, version : 0.0.0.0, horodatage : 0x56ba7d3a
Nom du module défaillant : ECT.exe, version : 0.0.0.0, horodatage : 0x56ba7d3a
Code d’exception : 0xc000001d
Décalage d’erreur : 0x00000000000288fe
ID du processus défaillant : 0x2094
Heure de début de l’application défaillante : 0x01d1a47b1cca156d
ID de rapport : 5a8e9521-106e-11e6-8fea-bcaec56f76e0
Filename contains no funny characters and does not exceed 255 characters. Files are not read-only or open in another application. UAC is disabled.
For the time being I've renamed ECT.exe so it does not run.
I haven't tried ECT with the 32 bits version of FO. <-- I suspect this is the root of the issue?
If it can help, I can run FO with a full log and send you the results.
Have a nice one!
Louis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Nikkho I kinda fixed the issue. It's a hack but it works.
I took the ECT.EXE file from the Plugins32 folder and copied it into the Plugins64 folder
No more error message ... although I'm using a 32 bit build of ECT.
Hope this helps someone.
Last edit: Louis Horvath 2016-05-04
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I got this response over Github. It makes a lot of sense :
"0xc000001d is "Illegal Instruction" so it seems the binary FileOptimizer is using has instructions your CPU doesn't support. Best guess is FileOptimizer is using an Intel-optimized binary and your somewhat old AMD CPU is missing the instruction set.
Assuming that's true, using a standard binary or binary optimized for amdfam10 should fix this."
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It makes sense. I am using ECT 0.2.1 builds from Malloc Voidstar (http://encode.ru/threads/2274-ECT-an-file-optimizer-with-fast-zopfli-like-deflate-compression?p=46539&viewfull=1#post46539).
Just waiting for the official ECT 0.3 binaries, already requested (http://encode.ru/threads/2274-ECT-an-file-optimizer-with-fast-zopfli-like-deflate-compression?p=47292&viewfull=1#post47292).
Im having a similar issue with ECT. It crashes about one in every 100 files it compresses. It wouldnt bother me too much, but it also pauses the compression cycle when it crashes. With only one thread, it takes quite a long time to sit through a few thousand files being compressed under maximum compression. Any chance of implementing multiple threads (this would at least allow the other threads to continue and dramatically reduce the effort on my part to click 'close' on the dialogue box. Or perhaps have a automatic recovery from crashed compression files?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Dr. Sassafras, have you reported the issue on the ECT tracker? ECT is itself multithreaded, it spans different threads per each deflate block.
FileOptimizer will be in a long term multithreaded, supporting the optimization of several files in paralel to speed it up, but this is a major change that will require a high effort.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, thanks. I will report the issue wth ECT. I took a quick look for them to report it, but didnt immedaly find the right website. Thanks also for your efforts. I konw the time that one needs to put into making changes that dont line up well with the way something was previously coded. Its a lot of effort!
Thanks so much for this amazing app. Ive been able to compress my images above and beyond what ImageOptim was able to do in most instances! Interestingly enough, after I cant get any more with ImageOptim, I switch to FileOptimizer. Run that a few times at maximum until I cant get any more compression. Then when I try ImageOptim again, a few of the files get compressed further. some even at 7% reduction!...?
Anyhow. thanks for the amazing app.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good afternoon! First of all, thank you SO MUCH for FileOptimizer! It has been SO useful!
So here we go. I've just downloaded the latest version of FO (8.30.1456).
I'm on Windows 7 pro, 64 bits, french. I'm using the x64 version of FO.
12 GB of ram. AMD 6 core processor. Rock solid system.
I am compressing HD-size PNGs : 1920x1080x24 bits. Uncompressed, these files are about 6mb.
Every time I compress a PNG, Windows throws me an error message, claiming ECT has crashed.
Here's what Windows has to say :
Source : Application Error
ID de l’événement :1000
Catégorie de la tâche :(100)
Niveau : Erreur
Mots clés : Classique
Utilisateur : N/A
Nom de l’application défaillante ECT.exe, version : 0.0.0.0, horodatage : 0x56ba7d3a
Nom du module défaillant : ECT.exe, version : 0.0.0.0, horodatage : 0x56ba7d3a
Code d’exception : 0xc000001d
Décalage d’erreur : 0x00000000000288fe
ID du processus défaillant : 0x2094
Heure de début de l’application défaillante : 0x01d1a47b1cca156d
ID de rapport : 5a8e9521-106e-11e6-8fea-bcaec56f76e0
Filename contains no funny characters and does not exceed 255 characters. Files are not read-only or open in another application. UAC is disabled.
For the time being I've renamed ECT.exe so it does not run.
I haven't tried ECT with the 32 bits version of FO. <-- I suspect this is the root of the issue?
If it can help, I can run FO with a full log and send you the results.
Have a nice one!
Louis
Thank you Louis.
Can you please file a ticket on ECT?
https://github.com/fhanau/Efficient-Compression-Tool/issues
Will send in a few minutes. Thanks.
Ticket #9, for your information
Nikkho I kinda fixed the issue. It's a hack but it works.
I took the ECT.EXE file from the Plugins32 folder and copied it into the Plugins64 folder
No more error message ... although I'm using a 32 bit build of ECT.
Hope this helps someone.
Last edit: Louis Horvath 2016-05-04
I got this response over Github. It makes a lot of sense :
"0xc000001d is "Illegal Instruction" so it seems the binary FileOptimizer is using has instructions your CPU doesn't support. Best guess is FileOptimizer is using an Intel-optimized binary and your somewhat old AMD CPU is missing the instruction set.
Assuming that's true, using a standard binary or binary optimized for amdfam10 should fix this."
Thank you very much for your help.
It makes sense. I am using ECT 0.2.1 builds from Malloc Voidstar (http://encode.ru/threads/2274-ECT-an-file-optimizer-with-fast-zopfli-like-deflate-compression?p=46539&viewfull=1#post46539).
Just waiting for the official ECT 0.3 binaries, already requested (http://encode.ru/threads/2274-ECT-an-file-optimizer-with-fast-zopfli-like-deflate-compression?p=47292&viewfull=1#post47292).
As an interim solution, you can try to replace ect.exe with the official builds from https://github.com/fhanau/Efficient-Compression-Tool/releases
latest version of your app.
ect.exe crashes when optimizing png
Win 10 64-bit. 4GB ram, cpu is Athlon II X4.
Last edit: bob joseph 2016-05-19
I followed your advice here, and DL'd the 64 bit version from the official build, and it works fine.
Also, as the previous person said, the ect.exe from the 32 bit folder also works.
Im having a similar issue with ECT. It crashes about one in every 100 files it compresses. It wouldnt bother me too much, but it also pauses the compression cycle when it crashes. With only one thread, it takes quite a long time to sit through a few thousand files being compressed under maximum compression. Any chance of implementing multiple threads (this would at least allow the other threads to continue and dramatically reduce the effort on my part to click 'close' on the dialogue box. Or perhaps have a automatic recovery from crashed compression files?
Dr. Sassafras, have you reported the issue on the ECT tracker? ECT is itself multithreaded, it spans different threads per each deflate block.
FileOptimizer will be in a long term multithreaded, supporting the optimization of several files in paralel to speed it up, but this is a major change that will require a high effort.
Ok, thanks. I will report the issue wth ECT. I took a quick look for them to report it, but didnt immedaly find the right website. Thanks also for your efforts. I konw the time that one needs to put into making changes that dont line up well with the way something was previously coded. Its a lot of effort!
Thanks so much for this amazing app. Ive been able to compress my images above and beyond what ImageOptim was able to do in most instances! Interestingly enough, after I cant get any more with ImageOptim, I switch to FileOptimizer. Run that a few times at maximum until I cant get any more compression. Then when I try ImageOptim again, a few of the files get compressed further. some even at 7% reduction!...?
Anyhow. thanks for the amazing app.
This can be possible depending on the file type, since File Optimizer and ImageOptim are using different libraries/plugins to optimize files.
Thanks for your comment.
Nikkho, still having this issue even today. I reverted to 32-bit ECT, but have 17 MPxl PNGs, so very slow (7+ hours CPU-time just in ECT), so hoping for AMD-compatible 64-bit binary. https://github.com/fhanau/Efficient-Compression-Tool/releases doesn't show any binaries, just source in .zip & .tgz. Issue filed in https://github.com/fhanau/Efficient-Compression-Tool/issues/38.
Last edit: TPS 2017-08-12
The issue is SSE4 compatability. Newer AMD CPUs will work.
https://en.wikipedia.org/wiki/SSE4#Supporting_CPUs
Use the x86 builds from encode.ru.
https://encode.ru/threads/2274-ECT-an-file-optimizer-with-fast-zopfli-like-deflate-compression
Thanks Skibicki.
Those are the exact builds I am using: https://encode.ru/threads/2274-ECT-an-file-optimizer-with-fast-zopfli-like-deflate-compression?p=53498&viewfull=1#post53498
x86 binary requires SSE2, while x64 requires SSE4. For x64, there are no other builds requiring less instructions sets (only AVR, which is more).
Replicating https://github.com/fhanau/Efficient-Compression-Tool/issues/38#issuecomment-321980143, an AMD A8-6410 apparently does support even SSE4a. How do I debug for y'all?
Thanks TPS.