haiwen / seafile-client

Seafile desktop client.
http://seafile.com
Apache License 2.0
471 stars 279 forks source link

Crash on Windows PC (Seafile-client v6.01) #854

Closed DorianVasco closed 4 months ago

DorianVasco commented 7 years ago

In the last days I experienced quite a few crashes of the client on Windows 10.

2017-01-06 12_19_05-

The client does not close, but all libraries stay 'unsynced', so I have to restart it.

applet.log says: [01/06/17 11:19:43]starting ccnet: ("-c", "C:/Users/mail/ccnet") [01/06/17 11:19:44]trying to connect to ccnet daemon...

[01/06/17 11:19:44]connected to ccnet daemon

[01/06/17 11:19:44]starting seaf-daemon: ("-c", "C:/Users/mail/ccnet", "-d", "E:/Seafile/seafile-data", "-w", "E:/Seafile") [01/06/17 11:19:45][Rpc Client] connected to daemon [01/06/17 11:19:45][RPC] failed to start rpc server: 511 Unknown service. [01/06/17 11:19:45]Unable to get config value use_proxy: Transport Error [01/06/17 11:19:46][Rpc Client] connected to daemon [01/06/17 11:19:46][RPC] failed to start rpc server: 511 Unknown service. [01/06/17 11:19:46]Unable to get config value use_proxy: Transport Error [01/06/17 11:19:47][Rpc Client] connected to daemon [01/06/17 11:19:50][Rpc Client] connected to daemon [01/06/17 11:19:50][MessageListener] connected to daemon [01/06/17 11:19:50]Unable to get config value download_limit: Config not exists [01/06/17 11:19:50]Unable to get config value upload_limit: Config not exists [01/06/17 11:19:51][Rpc Client] connected to daemon [01/06/17 11:19:51][Rpc Client] connected to daemon [01/06/17 11:19:54]The latest version is 5.0.4 [01/06/17 12:08:31][ext] Failed to read command from extension(), error code 232

[01/06/17 12:08:31]failed to write response to shell extension: Die Pipe wird gerade geschlossen.

[01/06/17 12:19:19][Sea RPC] Bad response: 515 peer down. [01/06/17 12:19:19][Sea RPC] Bad response: 102 processor is dead. [01/06/17 12:19:19][Sea RPC] Bad response: 102 processor is dead. [01/06/17 12:19:19][Sea RPC] Bad response: 102 processor is dead. [01/06/17 12:19:19][Sea RPC] Bad response: 102 processor is dead. [01/06/17 12:19:19][Sea RPC] Bad response: 102 processor is dead.

ccnet.log: [01/06/17 11:19:43] ccnet-daemon.c(193): starting ccnet client 6.0.1 [01/06/17 11:19:43] ccnet-daemon.c(195): ccnet source code version 7438d94e6f93e0d61854d01acab47560e79f78a9 [01/06/17 11:19:43] ../common/session.c(132): using config file C:/Users/mail/ccnet\ccnet.conf [01/06/17 11:19:43] ../common/session.c(418): Listen on 127.0.0.1 13419 [01/06/17 11:19:43] ../common/session.c(290): Update pubinfo file [01/06/17 11:19:44] ../common/session.c(398): Accepted a local client [01/06/17 11:19:45] ../common/session.c(398): Accepted a local client [01/06/17 11:19:45] ../common/session.c(398): Accepted a local client [01/06/17 11:19:45] ../common/peer.c(943): Local peer down [01/06/17 11:19:45] ../common/peer.c(943): Local peer down [01/06/17 11:19:46] ../common/session.c(398): Accepted a local client [01/06/17 11:19:46] ../common/session.c(398): Accepted a local client [01/06/17 11:19:46] ../common/peer.c(943): Local peer down [01/06/17 11:19:46] ../common/peer.c(943): Local peer down

2017-01-06 12_19_11-seafile

2017-01-06 12_19_20-seafile

DorianVasco commented 7 years ago

I think these crashes occur because of too many files (+100.000) in one of my libraries. I found similar errors in this thread: https://forum.seafile.de/t/client-error-error-failed-to-index-files/2360/3

After zipping some older folders (with huge amounts of .php files) everything seems to be okay again.

Nevertheless, it would be great, if Seafile would handle these kinds of errors in a better and more user friendly way.