Bitdefender causes Boxcryptor to crash due to Out Of Memory

danielsun

Boxcryptor has been crashing daily since its last update (or my last windows update, whichever came last);
version 2.49.1965.
Edition Windows 10 Enterprise
Version 20H2
Installed on ‎7/‎8/‎2021
OS build 19042.1415
Experience Windows Feature Experience Pack 120.2212.3920.0

Here's an error that shows up in the Windows event viewer:
Log Name: Application
Source: .NET Runtime
Date: 1/7/2022 12:16:16 AM
Event ID: 1026
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: 3V4HQC2.main.archbalt.org
Description:
Application: Boxcryptor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0000008, exception address 76B1B522

Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name=".NET Runtime" />
<EventID Qualifiers="0">1026</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2022-01-07T05:16:16.4664329Z" />
<EventRecordID>33727</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>3V4HQC2.main.archbalt.org</Computer>
<Security />
</System>
<EventData>
<Data>Application: Boxcryptor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0000008, exception address 76B1B522
</Data>
</EventData>
</Event>

Florian

Hi danielsun,

I am very sorry for the inconvenience!

I believe that the underlying issue has something to do with a recent Windows Update and the Chromium Embedded Framework (CEF) that we use to render the Sign-in Window and other web-based components.

Hence, I just updated the packages to the latest version. An experimental version for it can be found here:
https://www.dropbox.com/s/nbojcqewxyyptr3/Boxcryptor_v2.50.2164_Setup.msi?dl=0

Edit: Updating the package unfortunately did not fix the issue

If this still does not help, you can try an alternative (and even more) experimental version of Boxcryptor that does not use CEF any more altogether and now relies on Microsoft's Webview2 instead:
https://www.dropbox.com/s/h3k1rc8kxc8jvxz/Boxcryptor_v2.50.2163_Setup.msi?dl=0

Edit 2: "Even more experimental" means that the Webview2 integration is not fully completed and tested yet. However, this only impacts the initial sign-in and provider linking for the Whisply integration. Other core Boxcryptor features are not affected by this change.

Note: On Windows 10 or below, you might have to install the Webview2 Runtime. We will let you know if it is missing, though.

Please let me know which version worked for you or if you still keep running into issues!

Best regards,
Florian

jhavens30

Florian The alternative (and even more) experimental version of Boxcryptor is working for me. No application crashes yet.

tcsmith

+1 Here for same problem.

More details: Boxcryptor does auto-start properly on Windows 10 reboot. Within a short time, the system tray icon turns red and disappears.

I would like to try Florian's solution and report back, but this is used in a small production environment so I'm hesitant to use an experimental version.

hkeach

I tried the CEF version but Boxcryptor is still crashing for me on Windows 10

Geoffw

I have a similar problem.
I have used Boxcryptor since the early days of the classic version and it has always worked reliably in the background.
In mid December I became aware that BoxCryptor was cashing about once a day. It was not happened at a specific time, although it may be after a set running time as I didn’t away spot that it had stopped for some time. It sometimes happened in the middle of the night.

This pc is used as a server. The BoxCryptor drive is shared and then mapped as a network drive on the 2 working PCs ( only one pc uploading and downloading to OneDrive also the working PC can be shut down while the sever syncs in the background.)
Every time BoxCryptor cashed in the w10 event log there is a .Net runtime error followed by an Application Error
Application: Boxcryptor.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code e0000008, exception address 76C3B522
Application Error
Faulting application name: Boxcryptor.exe, version: 2.49.1965.0, time stamp: 0x61657247
Faulting module name: KERNELBASE.dll, version: 10.0.19041.1415, time stamp: 0x2791d798
Exception code: 0xe0000008
Fault offset: 0x0012b522
Faulting process ID: 0x1c08
Faulting application start time: 0x01d7f7116094bc86
Faulting application path: C:\Program Files (x86)\Boxcryptor\Boxcryptor.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: 06d65b97-4bd1-489c-a96e-6cfe23795823
Faulting package full name:
Faulting package-relative application ID:
When I looked back the same error appeared for a few weeks in April 2021. They also appeared at various times on the 2 working pcs. Boxcryptor runs on these as a backup in case the server is down and I am not around to fix it. We are retired so they are not that heavily used.
The PCs all run W10 and are about 5 years old. 2 intel and one AMD.
I believe that I am running version 4.8.4084.0 of .NET 2 and 3.5 also present.
On the sever pc I have run >NET repair process and uninstalled and reinstalled Boxcryptor.
Run scf and dsim to check for corrupt system files. Tuesdays Microsoft update included some .NET stuff so I though that might help but it made no difference.

Florian

Hi everyone!
After some more research, we came to the conclusion that it is not related to Chromium Embedded Framework.

However, having more users reporting this issue we have reason to believe that this issue is related to a recent bug in Bitdefender: https://community.bitdefender.com/en/discussion/89709/out-of-memory-error

It appears that in a recent December update, Bitdefender causes itself and other apps to use up most of the system's memory, which results in Apps like Boxcryptor to fail with OutOfMemory errors at some point.

To overcome this issue, it is recommended to either uninstall Bitdefender or, if applicable, disable Advanced Thread Defense and then to restart the affected device.

If you run into these issues without having Bitdefender installed, please let us know, too!

Edit: Note that we are in contact with Bitdefender Support and will let you know as soon as we have an update from their side.

Best regards,
Florian

Florian

Florian
Hi everyone!

We noticed that the module atcuf32.dll (Bitdefender Active Threat Control Usermode Filter) gets loaded into our own process structure, most likely causing our application to crash once Bitdefender runs short on available System memory.

With our last Boxcryptor for Windows Release Version 2.50.2196 (2022-01-31), we added an incompatibility warning that shows when we this module is detected within our own process, leading to our FAQ entry here.

Best regards,
Florian

Florian

Hi everyone!

We finally got good news from Bitdefender Support:

[...]
Kindly know that the issue is caused by an incompatibility. We added a fix that will be available with the following signature update.
[...]

Also, on our test system, we could no longer reproduce the issue with the latest updates of Bitdefender Total Security:

Best regards
Florian