You are not logged in.
Pages: 1
Today we deployed an update to our client application, which uses mORMot v2.4.
Several Windows 10 users reported an Access Violation error (the typical "Access violation at address aaaaaa in module bbbbb (offset cccccc). Read of address dddddd.").
I reproduced the issue on a Windows 10 VM. I also tested the application after reverting to mORMot v2.3, and the error no longer occurs with that version.
On Windows 7 and Windows 11, the application works without any issues.
Unfortunately, I don't have access to a Windows 10 dev machine to debug this further.
Offline
If some of your clients still use Windows 10, you need to have a VM with Windows 10 for testing your app, for sure.
There could be a lot of reasons for this, potentially not part of mORMot itself.
Especially since you are the only one reporting such an issue with Windows 10.
Without any more information, difficult to understand what happens.
The regression tests did pass with no issue on Windows 10 e.g. tonight:
https://luti.tranquil.it/get_folder_res … 93aW5kb3dz
Offline
While trying to set up remote debugging, I disabled Optimization in the project options - Building > Delphi Compiler > Compiling, and now the application works without any issues on Windows 10.
Very strange.
Offline
Pages: 1