Hello,
we are using SeaDrive client v0.7 on Windows 10 Prof.
When opening a word document with Microsoft Word 2010 (Office 2010) SeaDrive completely crashes. It is not possible to save a word file. Is this a known issue?
I tried it with and without the “Sync Microsoft / Libre office temp files” option. In both scenarios it crashes. It happens with every PC (tried 7 different PCs).
Any ideas?
Thanks in advance!
This is what the seadrive-gui.log says:
[06/12/17 11:28:50] Seadrive daemon process crashed with code -1073741819
[06/12/17 11:28:50] Exiting with error: SeaDrive unvorhergesehen ausgeworfen
[06/12/17 11:28:51] failed to get seadrive.events: ‘[’ or ‘{’ expected near end of file
[06/12/17 11:28:51] failed to get sync notification: ‘[’ or ‘{’ expected near end of file
[06/12/17 11:28:51] failed to get global sync status: ‘}’ expected near end of file
[06/12/17 11:28:51] failed to get sync errors: unable to decode byte 0xc6 near ‘H’
[06/12/17 11:28:52] failed to get seadrive.events: ‘[’ or ‘{’ expected near ‘’
[06/12/17 11:28:52] failed to get global sync status: ‘[’ or ‘{’ expected near end of file
[06/12/17 11:28:52] failed to get sync errors: ‘[’ or ‘{’ expected near ‘failed’
[06/12/17 11:28:53] failed to get seadrive.events: ‘[’ or ‘{’ expected near end of file
[06/12/17 11:28:53] failed to get sync notification: ‘}’ expected near end of file
[06/12/17 11:28:53] failed to get global sync status: ‘}’ expected near end of file
[06/12/17 11:28:53] failed to get sync errors: ‘[’ or ‘{’ expected near ‘failed’
[06/12/17 11:28:53] SeaDrive unvorhergesehen ausgeworfen
[06/12/17 11:28:53] app event loop exited with 1
This seems to be related:
UPDATE: Only happens with MS Word 2010, not Excel 2010 or Powerpoint 2010 for example. So saving excel sheets works… strange.
I’m new to Seafile and currently playing around with this software.
I can observe the same behaviour using MS Word 2010 (modifying the original Seafile Readme.doc is enough). Same error-code. (newest non-beta versions; Win 7 client; Ubuntu LTS 16.04 Server with SQlite)
Before trying to modify a MS Word document, my first check was using git, which also fails completely (official git-bash for windows; git totally unusable!).
I will be curious to see what others are experiencing, but for the moment i am very very disappointed as my first two things i tried were not working (while i was already scared of the dokany-based approach).
Interesting! So this seems to be a bug in GIT?!? Crazy! The 0.6.2 client works flawless 
I downgraded my customer’s clients to 0.6.2 now.
Not that it matters but just for the protocol: I am using mySQL.
Greetings from Germany
We’ll look into the issue and find a solution asap.
Those are .doc files created with MS Word 2010. I could provide a sample file if needed.
Not a solution, just a thought.
Be aware that you need to have a certain patch level for Office 2010 on Windows 10 to work properly. Otherwise it’s not officially supported. We’ve had several issues with Office because of this with many different clients. An upgrade to Office 2016 solved it in the end.
Sorry, but I think this is totally unrelated. It’s not office which is crashing and Seadrive has no list of programs it can be used with.
Seadrive is a generic virtual drive which should support any kind of file and should handle any possible error case. It shouldn’t crash in any situation - no matter if there is a software trying to access files with 100 threads, one that heavily seeks in large files or one that just reads or modifies a file.
That’s why I wrote this 
Hi,
Unfortunately I cannot reproduce your problem. Can you turn on debugging log and reproduce it?
You need to set an system environment variable on Windows: SEADRIVE_DEBUG=all
Once you reproduce the problem, please send me the seadrive.log. seadrive-gui.log doesn’t help.
Thanks
We built a binary with crash report. You can download it here: https://download.seafile.com/f/d3cfc94c3b/?raw=1 After installation and if the application crashes, you can find a dump file in C:\users\username\seadrive\logs\dumps folder. Please upload it to https://download.seafile.com/u/d/0d2057680b/
Note that the debug log file seadrive.log still helps, if you can enable debug log and send me the log too, it would be great.
Thanks
Some logs after setting SEADRIVE_DEBUG=all
seadrive-gui.log:
[06/19/17 14:44:08] Seadrive daemon process crashed with code -1073741819
[06/19/17 14:44:08] Exiting with error: SeaDrive unvorhergesehen ausgeworfen
[06/19/17 14:44:09] failed to get seadrive.events: unable to decode byte 0x86
[06/19/17 14:44:09] failed to get sync notification: unable to decode byte 0x86
[06/19/17 14:44:09] failed to get global sync status: unable to decode byte 0x86
[06/19/17 14:44:09] failed to get sync errors: '[' or '{' expected near 'x'
[06/19/17 14:44:10] failed to get seadrive.events: unable to decode byte 0x86
[06/19/17 14:44:10] failed to get sync notification: unable to decode byte 0x86
[06/19/17 14:44:10] failed to get global sync status: unable to decode byte 0x86
[06/19/17 14:44:10] failed to get sync errors: unable to decode byte 0x83
[06/19/17 14:44:10] SeaDrive unvorhergesehen ausgeworfen
[06/19/17 14:44:10] app event loop exited with 1
[06/19/17 14:44:10] Unmounting before exit
[06/19/17 14:44:10] [Daemon Mgr] stopping seadrive daemon
seadrive.log
Let’s see if you can work with that. I don’t think it’s a good design-decision to put language-dependent output in this log, but well…
Hi @sascha
I’ve updated the download link above. It contains a possible fix to the problem. User from another thread reported improvements after installing this version. But there is still a case that it could crash. So could you test this version as well and provide feedback? If it crashes again, please also provide seadrive.log and the dump file.
Thanks.