elfin hawk
We have also created an issue link of the same with more details: https://github.com/electron/electron/issues/49808
We were having, in our Windows 10 & 11 builds, Electron version 30.5.1, which we upgraded to 36.9.1, currently rolled out to 60% of users.
The issue at hand is that for a few users, we are getting a Sentry log which hints at a possible crash of the renderer process with this log [more screenshots attached]. Looking at the breadcrumbs we figured that he is able to interact with the app but after doing some actions this happens.
DelayLoad-LastError 193
DelayLoad-ModuleName ffmpeg.dll
As per our electron-builder-win-config file, we build the complete Windows application in ia32 architecture, and we had checked from our build machine the arch this ffmpeg.dll post installation was also of the 32-bit arch type [we did this to rule out the arch mis-match scenario].
When looking for this similar issue at github, we found that there was a fix done for this.
Similar issue: https://github.com/electron/electron/issues/47766
Fixed Link: https://github.com/electron/electron/pull/47768
We wanted to understand that if it was backported to 36.x.y, then how is this DelayLoad-ModuleName error getting logged to Sentry for users using the electron v36.9.1. Also, we were curious that this is happening only for ffmpeg.dll or any other similar DLL files that can be corrupted or removed as well. [Till now Sentry has only logged for ffmpeg.dll].
Any scenario that can manipulate these files during runtime?
digital osprey