Strange startup-bug in FileOptimizer 17

Javier Gutiérrez Chamorro (Guti) Open source projects

Brought to you by: nikkho

#143 Strange startup-bug in FileOptimizer 17

Milestone: 17.x

Status: open

Owner: Nikkho

Labels: None

Updated: 2025-10-15

Created: 2025-09-25

Creator: LeTiger

Private: No

Strange semi-bug with FileOptimizer since version 17, never seen this with earlier FO-versions.
Sometimes Windows yells about "Access violation" when I start FO.
(I've never seen this before, and I've used FO for years)
But when I click OK-button FO still starts and always works flawlessly.
Strangely this "Access violation" does not happen every time. Just sometimes, I'd say 10-15% of starts begin with "Access violation" -window?
Using Windows 10 Pro UK 64-bit.
Example picture as an attachment. Sorry that I have only one example picture, this is so random...

1 Attachments

FO_bug_picture.png

Discussion

LeTiger - 2025-09-25

2nd try to add attachment...

Last edit: LeTiger 2025-09-25

FO_bug_picture.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nikkho - 2025-09-26

Thank you for your report. Can you please provide more details?
When does the error exactly happen? Is after doing some action or while loading? Is the main window showing when the popup appears or not yet visible?
If you launch FO with no parameters the error still happens occasionaly?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

LeTiger - 2025-09-27

Happens immediately before actual FO-window opens, and FO always starts/works ok when I click OK-button in error window. I open FO by directly starting .EXE (FileOptimizer64.exe), I don't use automation or scripts or cmdline-options with FO. It wouldn't surprise me if this has something to do w/ soon ending W10-updates? But no other issues with W10 so far. And this is 1st time I've seen this. Just strange. But if there are no other reports of such issues maybe we should forget about this one? FO still does work OK after this unnecessary error-window so maybe it's just strange anomaly? I have no problems with my other programs, none. Another just captured error-picture included just in case.
I know that designers/coders always want to perfect their work (I do), but I'd forget this one if there is no known common problem?

FO-startup_Access_violation.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nikkho - 2025-09-27

Thank you so much. It could be either related to W10 Updates as you state (I myself am running W11 with no issues), or either due to FO 17.10 being upgraded to latest C++ Builder 13; or maybe an incompatibility with both.

I shall review the initialization code before main window opens, maybe there is a problem never noticed before, but it does not seem very probable.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rick - 2025-10-06

Same issue here, with some additional content:

on a win2019 server, the issue (Access violation, before the main window ~ close, then everything is nominal), appears every time I run the program as Administrator, but never (so far) when I run it as regular user

on a Linux machine (ubuntu 24.04, wine 9.0, 64bit prefix configured as Win7), the issue appears every time.

Hope this helps, TIA and keep up the good work!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

LeTiger - 2025-10-06

So it's not Only my problem - kind of happy (or not!) to hear. Because Nikkho just mentioned "FO 17.10 being upgraded to latest C++ Builder 13". Maybe some kind of a compatibility-problem with C++ Builder 13? More error-reports are certainly needed...
This might be a problem to someone who tries to automate/script FO. Or they just have to use older versions, no such problem with pre-17 -versions. And even 17.10 seems to be working OK for 99% of users?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Nikkho - 2025-10-08
  
  I have updated to lastest C++ Builder 13 September Update Patch, and compiled all binaries. Can you test with them?
  https://sourceforge.net/p/nikkhokkho/code/HEAD/tree/trunk/FileOptimizer/Win64x/Release/
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

rick - 2025-10-08

Same conditions, same issues (pls see attached screenshots).

Just out of curiosity, what happens around offset 0x410EF (since this is common to otherwise very different environments ~ at least here)

linux_user.png

win_admin.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

LeTiger - 2025-10-13

Tested versions 05092025 and 08102025, started 10 times from icon;

older version (FileOptimizer 17.10.2857 (x64) Sep 5 2025)
failed 4 times with read and write errors.

newer version (FileOptimizer 17.10.2857 (x64) Oct 8 2025)
failed 1 time with write error, see attached image.

So newer is obviously better with W10. Both versions started w/o problems after I clicked ok to those error-messages. So still no serious issue IMO, but still interesting.

FO_1710_Oct_08_startup_error.png

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
- Nikkho - 2025-10-15
  
  Thank you so much for the testing. I have been reviewing the initialization code, and have not found any problems. So I guess it should be a bug in latest C++ Builder combined with Windows 10. This will also confirm that when patched gets better.
  
  If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.