Page 1 of 2

Invalid Access To Memory Location

Posted: Mon Aug 30, 2021 2:12 pm
by thefunkyjoint
One of the users of my app is getting this error :

Error loading libcef.dll
Error code : 0x000003E6
Invalid Access To Memory Location

It's very odd , i never saw this in my machine and even never see with any other user.

He uses Windows 7 Professional, already tried to format the machine and reinstall Windows , but no lucky, same error remains.

I've noticed the error is generated by the subprocesses, so a lot of windows with the error message popups until i kill the processes.

Any ideas ? :?

Re: Invalid Access To Memory Location

Posted: Mon Aug 30, 2021 2:29 pm
by salvadordf
Please, enable the debug log in verbose mode and post it here or in private if necessary.

Try disabling the hardware acceleration too.

Re: Invalid Access To Memory Location

Posted: Mon Aug 30, 2021 3:53 pm
by thefunkyjoint
I tried it , but as soon as i call

GlobalCEFApp.LogFile := c:\folder\dcef.log';
GlobalCEFApp.LogSeverity := LOGSEVERITY_VERBOSE;
GlobalCEFApp.StartMainProcess;

The app crashes on the user machine and no log file is generated :shock:

So far is only one user, but because he formatted the machine and reinstalled Windows, i'm really intrigued about what is causing the issue...

Anything else i could try ?

Re: Invalid Access To Memory Location

Posted: Mon Aug 30, 2021 3:55 pm
by thefunkyjoint
salvadordf wrote: Mon Aug 30, 2021 2:29 pm Try disabling the hardware acceleration too.
How can i do this ?

Re: Invalid Access To Memory Location

Posted: Mon Aug 30, 2021 5:04 pm
by salvadordf
thefunkyjoint wrote: Mon Aug 30, 2021 3:55 pm
salvadordf wrote: Mon Aug 30, 2021 2:29 pm Try disabling the hardware acceleration too.
How can i do this ?
The hardware acceleration is enabled when you set GlobalCEFApp.EnableGPU to True before the GlobalCEFApp.StartMainProcess call in the DPR file. That property is disabled by default.

It's estrange that the application crashes as soon as the it runs with a debug log.
Does the Windows user account have write privileges in the drive where the application is located?

Re: Invalid Access To Memory Location

Posted: Mon Aug 30, 2021 6:25 pm
by thefunkyjoint
salvadordf wrote: Mon Aug 30, 2021 5:04 pm It's estrange that the application crashes as soon as the it runs with a debug log.
Does the Windows user account have write privileges in the drive where the application is located?
Actually it crashes with or without the log.

Here is what i tried :

- Disable hardware acceleration
- Set singleprocess = true
- Run as administrator

Nothing helps, same error. I'll keep doing tests and post the results here.

Re: Invalid Access To Memory Location

Posted: Mon Aug 30, 2021 6:58 pm
by salvadordf
Try the official CEF sample application on that computer :
https://cef-builds.spotifycdn.com/cef_binary_92.0.27%2Bg274abcf%2Bchromium-92.0.4515.159_windows64_client.tar.bz2

And also try running the MiniBrowser demo. That demo has the debug log enabled.

Re: Invalid Access To Memory Location

Posted: Mon Sep 06, 2021 12:53 pm
by thefunkyjoint
I've tested the minibrowser demo on the same machine and the same error occurs, as attached.

The error is in portuguese, but the equivalent in english is : "Invalid Access to Memory Location". The crash occurs right after i try to open the minibrowser demo.

This is very odd as only with this specific user the issue happens. He already formatted the machine and reinstalled Windows, but no lucky :?

https://ibb.co/4FRjwFG

Re: Invalid Access To Memory Location

Posted: Mon Sep 06, 2021 1:00 pm
by thefunkyjoint
One specific thing i do is, only deploy the necessary locales file :

GlobalCEFApp.LocalesRequired := 'en-US,en-GB,pt-BR,pt-PT';

Could this be the issue ?

Re: Invalid Access To Memory Location

Posted: Mon Sep 06, 2021 1:21 pm
by salvadordf
There are many suggestions to fix similar errors. Search "LoadLibrary error 998" to see more possible fixes.

Check these things :
  • The graphics card drivers are fully updated.
  • Windows is fully updated.
  • The CEF binaries are correctly updated and/or installed in the right directory.
  • Test what happens with all the files from the CEF binaries.
  • Disable the antivirus to see if it deletes or blocks any of the CEF files.