Hi, I find that png file takes considerably long time to optimize in version 16.00.2746 than the previous version 15.90.2730.
Using 15.90.2730, a large png can be optimized in around 5 hour in my old computer.
Using 16.00.2746, the same png cannot be completed for more than 24 hour in my new computer.
I use loseless optimization.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same thing here. I'm using many very similar PNGs, most of them complete within 30 sec - 2 minutes and then you have a picture with similar features that goes 100% core usage for 5+ hours on step 12. Using a Ryzen 5 2400G processor.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Louis, but is the problem png optimized successfully on 15.90.2730?
My case is the problem png has no problem on older version, but has problem on new version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the delay.
I think I figured it out. It's a configuration issue backed up by a quirky bug.
The way I work, every new version I extract the new version to a folder of it's own and then copy the FileOptimizer64.ini file into it.
There's been some changes between 15.x and 16.x so, logically, if something goes wrong, you'd think changes in the .INI could be the cause. But I deleted the .INI file and the issue persisted.
So I did the next best thing. I clicked on "Restore defaults" in the options menu and re-entered my specifications. It's all working now.
I can't see any important differences between the .INI (differences are all on the cosmetic side).
The logical answer is that "Restore defaults" does more than just reset the .INI file.
Note : The log files seem to indicate the program is running fine but stops at step 12 (ECT) without an error message or anything.
Since FileOptimizer disables console output I can't see what message ECT is telling us before going into an infinite loop.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you Louis. On the log file you should have the full command line used for all plugins. You can manually enter them on a console and see the output.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Command line : D:\Users\celeri\DOWNLO~1\!APPLI~1\FILEOP~1.277\PLUGIN~2\advpng.exe -z -q -4 -i 30 "C:\Users\celeri\AppData\Local\Temp\FileOptimizer_Input_1215_asndynmto.png"
PNG file is not found BUT here's the file I found in the temp folder : FileOptimizer_Input_9430_asndynmto.png
Tried the command line (and removed the -q) and got this :
Command line : D:\Users\celeri\DOWNLO~1\!APPLI~1\FILEOP~1.277\PLUGIN~2\advpng.exe -z -q -4 -i 30 "C:\Users\celeri\AppData\Local\Temp\FileOptimizer_Input_1215_asndynmto.png"
PNG file is not found BUT here's the file I found in the temp folder : FileOptimizer_Input_9430_asndynmto.png
Tried the command line (and removed the -q) and got this :
Batch file revealed no error. Therefore you will need to debug the output on your side.
If you need the PNGs I was working on, just ask. I can also give you my full system / program config.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also when ECT was running in loop my computer couldn't go into sleep.
Sounds an awful lot like an issue with ECT. If it happens rarely than it might be CPU specific.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CONCLUSION
Rolling ECT back to version 0.9.1 has resolved the issue! 725 compressed .PNG files later and no issue to report.
At least we know this is NOT a FileOptimizer issue!
I also noticed ECT is up to version 0.9.4. I might test to see how that version behaves (assuming I can find a compiled binary). https://github.com/fhanau/Efficient-Compression-Tool/releases
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Tried ECT 0.9.4 and about 5 minutes into the process ... infinite loop again and ECT never returns a result.
Since this does not seem to happen to everyone I am pretty sure this is CPU bound (that is a hunch). I will try to contact fhanau to let him know of the issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Update on that ECT issue.
- Symptom : ECT keeps on compressing the same file forever, requiring a break. It seems to happen randomly and is not caused by one specific file.
- Issue affects ECT 092, ECT 093 and ECT 094
- Seems to affect specific people so might be CPU-dependent (I'm using an AMD Ryzen 5 2400 CPU)
- Caused by the customization string (switch with only numbers) (-90032)
- ECT 091 works absolutely fine so temporary solution is to go back to that version
- Not caused by FileOptimzer
- Not caused by multi-threading
- Not caused by the --alfilters switch
- Tested on a pack of 3375 files so results are pretty definitve.
Hi, I find that png file takes considerably long time to optimize in version 16.00.2746 than the previous version 15.90.2730.
Using 15.90.2730, a large png can be optimized in around 5 hour in my old computer.
Using 16.00.2746, the same png cannot be completed for more than 24 hour in my new computer.
I use loseless optimization.
ECT has been updated in between 15.90 and 16.00. Do you know what is the plugin slowing down the process?
Let me have a test first.
Of course! Let me know.
Hi I try to optimize a file for more than 24 hour. I think it stuck at ECT 12/16.
See the screenshot attached.
Same thing here. I'm using many very similar PNGs, most of them complete within 30 sec - 2 minutes and then you have a picture with similar features that goes 100% core usage for 5+ hours on step 12. Using a Ryzen 5 2400G processor.
And also is the problem with ECT execution?
Hi Louis, but is the problem png optimized successfully on 15.90.2730?
My case is the problem png has no problem on older version, but has problem on new version.
Sorry for the delay.
I think I figured it out. It's a configuration issue backed up by a quirky bug.
The way I work, every new version I extract the new version to a folder of it's own and then copy the FileOptimizer64.ini file into it.
There's been some changes between 15.x and 16.x so, logically, if something goes wrong, you'd think changes in the .INI could be the cause. But I deleted the .INI file and the issue persisted.
So I did the next best thing. I clicked on "Restore defaults" in the options menu and re-entered my specifications. It's all working now.
I can't see any important differences between the .INI (differences are all on the cosmetic side).
The logical answer is that "Restore defaults" does more than just reset the .INI file.
Note : The log files seem to indicate the program is running fine but stops at step 12 (ECT) without an error message or anything.
Since FileOptimizer disables console output I can't see what message ECT is telling us before going into an infinite loop.
Thank you Louis. On the log file you should have the full command line used for all plugins. You can manually enter them on a console and see the output.
Sadly ECT went into a loop again. I will definitely try the command line BUT this doesn't happen on the same file every time. Keep you posted.
Command line :
D:\Users\celeri\DOWNLO~1\!APPLI~1\FILEOP~1.277\PLUGIN~2\advpng.exe -z -q -4 -i 30 "C:\Users\celeri\AppData\Local\Temp\FileOptimizer_Input_1215_asndynmto.png"PNG file is not found BUT here's the file I found in the temp folder : FileOptimizer_Input_9430_asndynmto.png
Tried the command line (and removed the -q) and got this :
As expected it worked fine but it did go into an infinite loop when called from Fileoptimizer.
I'll try to create a batch file to compress a whole bunch of .PNGs in a row with ECT and see if I can get an error message.
Command line :
D:\Users\celeri\DOWNLO~1\!APPLI~1\FILEOP~1.277\PLUGIN~2\advpng.exe -z -q -4 -i 30 "C:\Users\celeri\AppData\Local\Temp\FileOptimizer_Input_1215_asndynmto.png"PNG file is not found BUT here's the file I found in the temp folder : FileOptimizer_Input_9430_asndynmto.png
Tried the command line (and removed the -q) and got this :
As expected it worked fine but it did go into an infinite loop when called from Fileoptimizer.
I'll try to create a batch file to compress a whole bunch of .PNGs in a row with ECT and see if I can get an error message.
Batch file revealed no error. Therefore you will need to debug the output on your side.
If you need the PNGs I was working on, just ask. I can also give you my full system / program config.
Also when ECT was running in loop my computer couldn't go into sleep.
Sounds an awful lot like an issue with ECT. If it happens rarely than it might be CPU specific.
@nikkho Do you think upgrading / downgrading ECT will work?
Will try and come back to you
Last edit: Louis Horvath 2023-03-06
Rolled ECT back to the one included in FileOptimizer 15.90.1730 (ECT version 0.9.1). Testing in progress (so far so good).
CONCLUSION
Rolling ECT back to version 0.9.1 has resolved the issue! 725 compressed .PNG files later and no issue to report.
At least we know this is NOT a FileOptimizer issue!
I also noticed ECT is up to version 0.9.4. I might test to see how that version behaves (assuming I can find a compiled binary).
https://github.com/fhanau/Efficient-Compression-Tool/releases
Thank you for the findings Louis. Glad to hear FO is safe!
Tried ECT 0.9.4 and about 5 minutes into the process ... infinite loop again and ECT never returns a result.
Since this does not seem to happen to everyone I am pretty sure this is CPU bound (that is a hunch). I will try to contact fhanau to let him know of the issue.
I added an issue to the ECT Github page.
https://github.com/fhanau/Efficient-Compression-Tool/issues/125
Feel free to add / correct if there's missing information.
Update on that ECT issue.
- Symptom : ECT keeps on compressing the same file forever, requiring a break. It seems to happen randomly and is not caused by one specific file.
- Issue affects ECT 092, ECT 093 and ECT 094
- Seems to affect specific people so might be CPU-dependent (I'm using an AMD Ryzen 5 2400 CPU)
- Caused by the customization string (switch with only numbers) (-90032)
- ECT 091 works absolutely fine so temporary solution is to go back to that version
- Not caused by FileOptimzer
- Not caused by multi-threading
- Not caused by the --alfilters switch
- Tested on a pack of 3375 files so results are pretty definitve.
If you experience the same issue please share your experience here and on the ECT Github page https://github.com/fhanau/Efficient-Compression-Tool/issues/125
Last edit: Louis Horvath 2023-03-14
All tests done, now it's up to @fhanau to find out where the issue is.
Got a beta version from @fhanau. Testing as we speak.
Last edit: Louis Horvath 2023-03-30
Great Louis. Please keep me posted and do not hesitate sharing this beta.