Cryptomator Crashing #3351
Comments
|
@Kapowpenguin1 Can you provide us with the crash log? Follow these instructions to create one:
In your home folder you should see the file |
infeo
added
the
state:awaiting-response
unfortunately, i don't seem to see any file of the sort. i looked under "C:", "C:\Users\user", and did a search for "cryptomator_crash" using WizTree [file explorer was taking too long] and none of those yielded any results. however, i see that java seems to be involved in this process. does cryptomator use a specific version of java? bc i know that i changed the PATH for java while i was installing FIleCloud [to jdk 11.0.2] |
Strange. In our forum we have another user reporting the exactly same problem (thread is in german). I also asked for a crash log and the user also reported that none was created. @Kapowpenguin1 Can you post the value of your PATH variable then? $env:PathAdditionally, i would like to ensure, that in the above crashlog instructions the copied config file is really used. To do so, can you repeat the instructions, but add between step 4 and 5 a new step?
Before performing step 5, please check the current version in the general preferences, tab "Updates". It should be |
infeo
added
state:awaiting-response
PATH variable: 4.5: same deal, went through the modified steps [and cryptomator showed 1.99.0] but still no cryptomator_crash anywhere |
|
Okay, let's take out bigger guns. You can download a debug version of Cryptomator here To ensure, that it is a valid installer, you can use its SH256-Checksum: The debug version always opens a terminal. In the terminal, application log and output of the gui framework is shown. @Kapowpenguin1 Can you uninstall current Cryptomator version and install the debug one? Then start it with the following command in Powershell: & "C:\Program Files\Cryptomator\Cryptomator.exe" 2>&1 > .\cryptomatorDebug.logTrigger the crash and afterwards paste the content of |
infeo
added
state:awaiting-response
the log is too big so i think i have to share it as a file |
|
@Kapowpenguin1 thanks for the log. Unfortunately, another let-down, there is no sign, why the app terminated suddenly. I followed the track of "FileCloud app changed something", but on my Windows 11 VM after installing FileCloud Drive, i could still open and use the file picker dialog with the choose button. If you install Cryptomator 1.11.1, does it then work? Another guess of me is an external applicaiton, e.g. antivirus software. It could kill Cryptomator immediately with the |
infeo
added
state:awaiting-response
unfortunately, 1.11.1 seems to have the same issue. |
i decided to try using procmon to see what cryptomator was up to: |
That is indeed a good idea! @Kapowpenguin1 Can you provide the procmon log file by storing/exporting it? Since those can be quire big, i think it is enough to start the procmon capture right before you click the choose button in the Cryptomator GUI. You can start or stop the capture with "CRTL+E" shortcut. |
infeo
added
state:awaiting-response
Logfile.CSV |
|
The error code contained in it is already helpful: -1073741819 , meaning 0xC0000005 or @Kapowpenguin1 Can you send this minidump? It's name should be something like |
infeo
added
state:awaiting-response
Cryptomator.exe.21796.dmp |
infeo
removed
the
state:awaiting-response
|
Finally! We found the culprit: @Kapowpenguin1 Are you still using Dokan as the volume type? If not, i suggest to remove it (can be done via system settings) and try again. |
infeo
added
the
state:awaiting-response
i have no idea what dokan is. my settings > virtual drive > default volume type has always been "Automatic" |
|
@Kapowpenguin1 You can check out the docs what Dokany is. Ensure, that WinFsp is installed (by using the Cryptomator EXE installer). Afterwards you can uninstall Dokany. |
infeo
added
state:awaiting-response
i looked up "dokany" under "installed apps" in settings, uninstalled it, and cryptomator immediately began working properly again. it's so weird bc it wasn't giving me any problems before, but ig it was the culprit for some reason? i don't get it. anyways, i appreciate your guidance through this |
infeo
removed
the
state:awaiting-response
|
Issue will be fixed with #3361. |
Please agree to the following
Summary
Cyptomator abruptly closes when attempting to add an existing vault
What software is involved?
Volume Type
None
Steps to Reproduce
Expected Behavior
some sort of dialogue allowing me to select a directory/file
Actual Behavior
app crashes
Reproducibility
Always
Relevant Log Output
Anything else?
cryptomator was working fine when i initially installed it. the only change i can remember making which may have impacted the ability of cryptomator to function properly was installing and configuring FileCloud on my system. but i'm not sure how exactly it would've affected cryptomator. i know it affected an install of stable diffusion i had, by changing the PATH of python, so something similar might've happened here. i'm just not sure what exactly
The text was updated successfully, but these errors were encountered: