Random crash when opening from tray

Hi,

It seams that Cryptomator randomly crashes while trying to maximise it from tray. It’s takes a bit of time for this to happen, as opening from try right after launch is ok.
This happens with or without a vault opened.
I do have logs enabled, i’ll add them here if requested.

OS: Windows 11 PRO 23H2 (22631.4751)
Cryptomator: 1.15.1 (smi-5571)

LE: While writing this, Cryptomator crashed when set back to tray.

Welcome to the Cryptomator Community :slightly_smiling_face:

crashes are not written to the regular log, but to a special crash log. To ensure the crash log is created, edit with admin permissions the file C:\Program Files\Cryptomator\app\Cryptomator.cfg and as first line in the JavaOptions section, add the following line:

java-options=-XX:ErrorFile=C:\Users\[YOUR USERNAME]\cryptomator_crash.log

where [YOUR USERNAME] must be replaced with the logged in accountname.

Afterwards, restart the Cryptomator app and trigger the crash. Once done, the crash log can be found at the above specified path. You can send us the regular and the crash log via mail at support@cryptomator.org .

Hi infeo,

Thank you for the info.
Sadly i can’t get the crash log to work.
I’ve added the line of code as suggested, but nothing happens after a crash.
Here is a partial from the Cryptomator.cfg:

java-options=$APPDIR\mods

-XX:Errorfile=C:\Users\mike\cryptomator_crash.log

Please assist me further so i can send the crash log.

my bad, i relied on old documentation. I corrected the command in my previous post.

Thank you for the updated version. It works now!
I’ll be sending the crash log to support as suggested.

@Just4 I looked into the crash log, important part is

---------------  S U M M A R Y ------------

Command Line: -Djpackage.app-version=1.15.1.5571 --enable-preview --enable-native-access=org.cryptomator.jfuse.win,org.cryptomator.integrations.win -Xss5m -Xmx256m -Dcryptomator.appVersion=1.15.1 -Dfile.encoding=utf-8 -Djava.net.useSystemProxies=true -Dcryptomator.logDir=@{localappdata}/Cryptomator -Dcryptomator.pluginDir=@{appdata}/Cryptomator/Plugins -Dcryptomator.settingsPath=@{appdata}/Cryptomator/settings.json;@{userhome}/AppData/Roaming/Cryptomator/settings.json -Dcryptomator.p12Path=@{appdata}/Cryptomator/key.p12;@{userhome}/AppData/Roaming/Cryptomator/key.p12 -Dcryptomator.ipcSocketPath=@{localappdata}/Cryptomator/ipc.socket -Dcryptomator.mountPointsDir=@{userhome}/Cryptomator -Dcryptomator.loopbackAlias=cryptomator-vault -Dcryptomator.showTrayIcon=true -Dcryptomator.buildNumber=msi-5571 -Dcryptomator.integrationsWin.autoStartShellLinkName=Cryptomator -Dcryptomator.integrationsWin.keychainPaths=@{appdata}/Cryptomator/keychain.json;@{userhome}/AppData/Roaming/Cryptomator/keychain.json -Djavafx.verbose= --module-path=C:\Program Files\Cryptomator\app\mods -XX:ErrorFile=C:\Users\mike\cryptomator_crash.log -Djpackage.app-path=C:\Program Files\Cryptomator\Cryptomator.exe -Djdk.module.main=org.cryptomator.desktop org.cryptomator.desktop/org.cryptomator.launcher.Cryptomator

Host: AMD Ryzen 5 3600 6-Core Processor              , 12 cores, 31G,  Windows 11 , 64 bit Build 22621 (10.0.22621.4391)
Time: Mon Feb 10 16:55:52 2025 GTB Standard Time elapsed time: 92.587300 seconds (0d 0h 1m 32s)

---------------  T H R E A D  ---------------

Current thread (0x00000247b61075f0):  JavaThread "QuantumRenderer-0" daemon [_thread_in_native, id=26772, stack(0x000000a04ee00000,0x000000a04f300000) (5120K)]

Stack: [0x000000a04ee00000,0x000000a04f300000],  sp=0x000000a04f2fe800,  free space=5114k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C  [d3d9.dll+0x18121]  (no source info available)
C  [d3d9.dll+0x475fa]  (no source info available)
C  0x00000247c5b53c1e  (no source info available)
C  0x00000247c5b548d2  (no source info available)
C  0x00000247c5b54379  (no source info available)
C  0x00000247c5b72fef  (no source info available)
C  [prism_d3d.dll+0x423a]  (no source info available)
C  0x00000247a613d187  (no source info available)

The last pc belongs to native method entry point (kind = native) (printed below).
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j  com.sun.prism.d3d.D3DSwapChain.nPresent(JJ)I+0 javafx.graphics@23.0.1
j  com.sun.prism.d3d.D3DSwapChain.present()Z+25 javafx.graphics@23.0.1
j  com.sun.javafx.tk.quantum.PresentingPainter.run()V+451 javafx.graphics@23.0.1
j  java.util.concurrent.Executors$RunnableAdapter.call()Ljava/lang/Object;+4 java.base@23.0.1
j  java.util.concurrent.FutureTask.runAndReset()Z+44 java.base@23.0.1
j  com.sun.javafx.tk.RenderJob.run()V+1 javafx.graphics@23.0.1
j  java.util.concurrent.ThreadPoolExecutor.runWorker(Ljava/util/concurrent/ThreadPoolExecutor$Worker;)V+92 java.base@23.0.1
j  java.util.concurrent.ThreadPoolExecutor$Worker.run()V+5 java.base@23.0.1
j  com.sun.javafx.tk.quantum.QuantumRenderer$PipelineRunnable.run()V+8 javafx.graphics@23.0.1
j  java.lang.Thread.runWith(Ljava/lang/Object;Ljava/lang/Runnable;)V+5 java.base@23.0.1
j  java.lang.Thread.run()V+19 java.base@23.0.1
v  ~StubRoutines::call_stub 0x00000247a6130fcd

siginfo: EXCEPTION_ACCESS_VIOLATION (0xc0000005), reading address 0x00000000000000ad

The file d3d9.dllis the Direct3D library. There seems to be a problem with your graphics driver. You can check with the dxdiag command, if everything is correctly setup. Also, some internet posts suggest that other software might interfere and cause a crash.

I’ve checked dxdiag and it shows no problems in all tabs. Oslo my diver is up to date (572.16).
Is there anything else i can check?

LE: Regarding RivaTuner. i don’t have it installed, But i do use the new Nvidia App and it has a similar option to display stats. Could that be a problem?

Update!

It might be fixed. Right after doing the dxdiag i haven’t been able to cause a crash anymore.
I’ve also tested the Nvidia App Overlay. With or without it it does not crash.
After a restart all is well. Here’s hoping it stays that way! :crossed_fingers:

I did see that i had 3 variants in file explorer quick menu.

I’ll wait till the next day to set this on as Solved. Just in case.

LE: I tested it one last time prior to clicking submit on this post and it crashed. :eyes:

Update!
Today all was fine. No crashes at all.
This randomness is not what i like, but if it stops, i’m happy.

Update!
No crash today.
I’ve also updated windows to KB5051989. No crashes after restart.
With the info provided above and prior posts, i fail to see a reason for the crash.

If i can further help some info i’ll do so, otherwise, for me, this topic is closed. (we can further discuss via the email i sent)

Update!
Just thought that i should mention this.
Ever since i switched from mounting from Drive to Folder i had no crashes.