fvogt added a comment.
In D23384#570331 <https://phabricator.kde.org/D23384#570331>, @ngraham wrote: > In D23384#570118 <https://phabricator.kde.org/D23384#570118>, @fvogt wrote: > > > Please try both of the following: > > > Done. Here are the log files: > > F7793378: kio-fuse.log <https://phabricator.kde.org/F7793378> Just as expected: unique: 4248, opcode: READ (15), nodeid: 13, insize: 80, pid: 24522 org.kde.kio.fuse: Read "Dean plays with Winnie.mov" 0 65536 org.kde.kio.fuse: Fetching cache for "Dean plays with Winnie.mov" kf5.kio.core: KLocalSocket(0x212cfd0) Jumbo packet of 65534 bytes kf5.kio.core: KLocalSocket(0x212cfd0) Jumbo packet of 65534 bytes unique: 4248, success, outsize: 65552 kf5.kio.core: KLocalSocket(0x212cfd0) Jumbo packet of 65534 bytes unique: 4250, opcode: GETATTR (3), nodeid: 13, insize: 56, pid: 24522 unique: 4250, success, outsize: 120 unique: 4252, opcode: READ (15), nodeid: 13, insize: 80, pid: 24522 org.kde.kio.fuse: Read "Dean plays with Winnie.mov" 153833472 36864 It first reads the header and then jumps to the file's end to read a few KiB there. Nothing kio-fuse can do about that, except trying to use `KIO:open` in the future, but that has some other drawbacks... > F7793379: strace output.log <https://phabricator.kde.org/F7793379> REPOSITORY R241 KIO REVISION DETAIL https://phabricator.kde.org/D23384 To: feverfew, fvogt, davidedmundson, dfaure, ngraham Cc: broulik, sitter, davidedmundson, kde-frameworks-devel, ngraham, LeGast00n, GB_2, michaelh, bruns
