0.7.0 client unstable?

I have a huge library, with big 700MB (or more) ISO files and seadrive client keeps crashing when trying to load stuff from them.

I understand my apps may be performing random access to these files but without random access capability this client is kind of worthless.

Also after the problem happens the S drive is still “taken” so I have to reboot to be able to use it as drive S again.

[06/14/17 21:22:46] Not unmounting because rpc client not ready.
[06/14/17 21:22:46] [Daemon Mgr] stopping seadrive daemon
[06/14/17 21:24:32] loaded 1 accounts
[06/14/17 21:24:32] seadrive gui started
[06/14/17 21:24:32] Using disk letter S:
[06/14/17 21:24:32] starting seadrive daemon: seadrive.exe “-d” “C:/Users/Andres/seadrive/data” “-l” “C:/Users/Andres/seadrive/logs/seadrive.log” “S:”
[06/14/17 21:24:36] Unable to get config value download_limit: Config not exists
[06/14/17 21:24:36] Unable to get config value upload_limit: Config not exists
[06/14/17 21:24:36] Switched to account https://files.andressm.org xbmc@no-ip.org ef767cd
[06/14/17 21:26:04] unknown type of seadrive event file-download.start
[06/14/17 21:26:19] unknown type of seadrive event file-download.done
[06/14/17 21:26:28] Seadrive daemon process crashed with code -1073741819
[06/14/17 21:26:28] Exiting with error: SeaDrive exited unexpectedly
[06/14/17 21:26:29] failed to get seadrive.events: ‘[’ or ‘{’ expected near ‘-’

[06/14/17 21:26:29] failed to get global sync status:

[06/14/17 21:26:29] failed to get sync errors: ‘[’ or ‘{’ expected near ‘`’

[06/14/17 21:26:30] failed to get global sync status:

[06/14/17 21:26:30] failed to get sync errors: unable to decode byte 0x88

[06/14/17 21:26:31] failed to get global sync status: end of file expected near end of file

[06/14/17 21:26:31] failed to get sync errors: ‘[’ or ‘{’ expected near ‘?’

[06/14/17 21:26:32] failed to get seadrive.events: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:32] failed to get global sync status: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:32] failed to get sync errors: ‘[’ or ‘{’ expected near ‘?’

[06/14/17 21:26:33] failed to get seadrive.events: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:33] failed to get global sync status:

[06/14/17 21:26:33] failed to get sync errors: ‘[’ or ‘{’ expected near ‘’

[06/14/17 21:26:34] failed to get seadrive.events: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:34] failed to get sync notification: premature end of input

[06/14/17 21:26:34] failed to get global sync status: ‘[’ or ‘{’ expected near ‘’

[06/14/17 21:26:35] failed to get global sync status: end of file expected near end of file

[06/14/17 21:26:35] failed to get sync errors: unable to decode byte 0xad near ‘H’

[06/14/17 21:26:36] failed to get seadrive.events: end of file expected near end of file

[06/14/17 21:26:36] failed to get sync notification: premature end of input

[06/14/17 21:26:36] failed to get global sync status: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:37] failed to get seadrive.events: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:37] failed to get sync notification: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:37] failed to get global sync status: ‘}’ expected near end of file

[06/14/17 21:26:38] failed to get seadrive.events: end of file expected near end of file

[06/14/17 21:26:38] failed to get global sync status:

[06/14/17 21:26:39] failed to get global sync status: ‘}’ expected near end of file

[06/14/17 21:26:40] failed to get global sync status: end of file expected near end of file

[06/14/17 21:26:41] failed to get global sync status:

[06/14/17 21:26:42] failed to get sync notification: ‘}’ expected near end of file

[06/14/17 21:26:42] failed to get global sync status:

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] [ext] Failed to read command from extension(), error code 232

[06/14/17 21:26:43] failed to write response to shell extension: The pipe is being closed.

[06/14/17 21:26:43] failed to get seadrive.events: end of file expected near end of file

[06/14/17 21:26:43] failed to get global sync status:

[06/14/17 21:26:44] failed to get seadrive.events: ‘[’ or ‘{’ expected near ‘’

[06/14/17 21:26:44] failed to get global sync status: end of file expected near end of file

[06/14/17 21:26:45] failed to get seadrive.events: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:45] failed to get sync notification: ‘[’ or ‘{’ expected near end of file

[06/14/17 21:26:45] failed to get global sync status:

[06/14/17 21:26:45] failed to get sync errors: ‘[’ or ‘{’ expected near ‘failed’

[06/14/17 21:26:45] SeaDrive exited unexpectedly
[06/14/17 21:26:45] app event loop exited with 1

[06/14/17 21:26:45] Unmounting before exit
[06/14/17 21:26:45] [Daemon Mgr] stopping seadrive daemon

Does this happened in 0.6.2 version?

Nope, I just tested, loaded an M3U file that points to two bin+cue images.
And it’s not random reads btw, I’m preloading the whole file in memory.

Hello,

I have the same error since i have installed the last version of the seadrive client. No error with the previous 0.6.2 version.

Regards,
Sylvain

@Sylvain_Rossi @fr500

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

@fr500 @Sylvain_Rossi

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

I uploaded my files.

Thanks. We’ve found the cause. We’ll provide a fixed version for testing soon.

@float You can find the updated version in the same download link. Please have a try and give feedback.

Thanks for the help!

sorry I wasn’t able to help, I wasn’t around for the weekend, I’ll test this tomorrow!

Still crashing here, added my crashdump

@fr500 I’ve updated the link again. Please have a try.

Yes! seems all’s good now, I just loaded a 2.8GB multipart medium and worked without a hitch.
Edit: and now it crashed again with another one.

Uploaded a new dump

Hi @fr500

The new crash seems to be caused by another related problem. We need to seadrive.log debug messages to find the cause. Could you enable the debug output and provide the log file?

Thanks.

It works for me but the browsing of the different folders is slow.

Good to hear. The slow browsing may be due to Windows explorer aggressively generating preview for files (especially for photo folders).