Windows 10 client crashes "ENFORCE(FAILING)"

Nextcloud Windows Client 3.2.2
Connected to Nextcloud 21.0.2
Windows version / build: 2004 / 19041.985

A short while (not much more than a minute) after the client connects to the server it crashes. This did not occur a few versions back, but I do not remember which.

Unhandled exception at 0x00007FFD11539800 (nextcloud_csync.dll) in nextcloud.exe: 0xC0000005: Access violation writing location 0x0000000000000000.

The logfile:

2021-05-31 18:18:24:308 [ info nextcloud.sync.networkjob.lscol ]:	LSCOL of QUrl("http://xxx.xxx.xxx.xxx/nextcloud/remote.php/dav/files/folders") FINISHED WITH STATUS "OK"
2021-05-31 18:18:24:308 [ debug nextcloud.sync.database.sql ]	[ OCC::SqlQuery::bindValue ]:	SQL bind 1 3711184153661606085
2021-05-31 18:18:24:308 [ debug nextcloud.sync.database.sql ]	[ OCC::SqlQuery::exec ]:	SQL exec "SELECT path, inode, modtime, type, md5, fileid, remotePerm, filesize,  ignoredChildrenRemote, contentchecksumtype.name || ':' || contentChecksum, e2eMangledName, isE2eEncrypted  FROM metadata  LEFT JOIN checksumtype as contentchecksumtype ON metadata.contentChecksumTypeId == contentchecksumtype.id WHERE parent_hash(path) = ?1 ORDER BY path||'/' ASC"
2021-05-31 18:18:24:309 [ info sync.discovery ]:	Processing "document1.pdf" | valid: false/true/false | mtime: 0/1588681193/0 | size: 0/2981893/0 | etag: ""//"" | checksum: ""//"" | perm: 0x7ffd0d07b198//0x7ffd0d07b198 | fileid: ""//"" | inode: 0/61731/ | type: CSyncEnums::ItemTypeSkip/CSyncEnums::ItemTypeFile/CSyncEnums::ItemTypeFile | e2ee: false/false | e2eeMangledName: ""/""
2021-05-31 18:18:24:309 [ debug nextcloud.sync.database.sql ]	[ OCC::SqlQuery::bindValue ]:	SQL bind 1 61731
2021-05-31 18:18:24:309 [ debug nextcloud.sync.database.sql ]	[ OCC::SqlQuery::exec ]:	SQL exec "SELECT path, inode, modtime, type, md5, fileid, remotePerm, filesize,  ignoredChildrenRemote, contentchecksumtype.name || ':' || contentChecksum, e2eMangledName, isE2eEncrypted  FROM metadata  LEFT JOIN checksumtype as contentchecksumtype ON metadata.contentChecksumTypeId == contentchecksumtype.id WHERE inode=?1"
2021-05-31 18:18:24:313 [ info sync.discovery ]:	checking checksum of potential rename  "document1.pdf" "SHA1:d9020c62d1de46266853e25bd0a1234567890abc" "SHA1:d9020c62d1de46266853e25bd0a1234567890abc"
2021-05-31 18:18:24:313 [ warning nextcloud.sync.discovery ]:	ENFORCE(FAILING) "document.pdf"
2021-05-31 18:18:24:313 [ warning nextcloud.sync.discovery ]:	instruction == CSYNC_INSTRUCTION_REMOVE false
2021-05-31 18:18:24:313 [ warning nextcloud.sync.discovery ]:	((*it)->_type == ItemTypeVirtualFile && instruction == CSYNC_INSTRUCTION_NEW) false
2021-05-31 18:18:24:313 [ warning nextcloud.sync.discovery ]:	((*it)->_isRestoration && instruction == CSYNC_INSTRUCTION_NEW)) false
2021-05-31 18:18:24:313 [ warning nextcloud.sync.discovery ]:	instruction CSyncEnums::CSYNC_INSTRUCTION_IGNORE
2021-05-31 18:18:24:313 [ warning nextcloud.sync.discovery ]:	(*it)->_type CSyncEnums::ItemTypeFile
2021-05-31 18:18:24:313 [ warning nextcloud.sync.discovery ]:	(*it)->_isRestoration  true
2021-05-31 18:18:24:313 [ fatal default ]:	ENFORCE: "false" in file libsync\discoveryphase.cpp, line 188

I think it’s better to file an issue at github

sounds similar to

1 Like