[Libreoffice-bugs] [Bug 70224] LibreOffice 1-byte disk reads
https://bugs.freedesktop.org/show_bug.cgi?id=70224 --- Comment #2 from ste...@hoefer.ch --- I forgot to mention: DOC and XLS files are loading fine. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70224] LibreOffice 1-byte disk reads
https://bugs.freedesktop.org/show_bug.cgi?id=70224 --- Comment #3 from ste...@hoefer.ch --- Yes, it doesn't matter whether profiles are new or existing, what software is installed, what Windows is installed, etc. The 1-byte reads however only have their adverse effect on Dokan based filesystems, NOT on native filesystems (NTFS, ...). My educated guess is the 1-byte reads always happen, but some NTFS caching mechanism or OS voodoo keeps them from mattering too much, while Dokan is simply not built to handle this large amount of micro reads and becomes very inefficient. After all, every single read() has to be rerouted from kernel space to user space, handled there by Dokan, then the Dokan based filesystem, and then rerouted to kernel space, where the OS completes the call. Dokan comes with a mirrorFS example, best way would be to install it and start from there. For now, we will convert all files from ODT/ODS to DOC/XLS, these are working fine, but I definitely *do* want to use ODF formats in the future for obvious reasons, so if anyone could fix this, I would appreciate it. UPDATE: The problem does NOT occur with OpenOffice 3.3 (found it on some older workstations and servers where people were not complaining :-) on SBS2003 and XP (didn't try Win7 yet). -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70224] LibreOffice 1-byte disk reads
https://bugs.freedesktop.org/show_bug.cgi?id=70224 --- Comment #4 from Urmas davian...@gmail.com --- What exact steps are needed to reproduce ReadFile API calls of 1 byte? What are 'read' system calls and how they are related to LO? Which file is read this way? -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70224] LibreOffice 1-byte disk reads
https://bugs.freedesktop.org/show_bug.cgi?id=70224 --- Comment #5 from ste...@hoefer.ch --- What exact steps are needed to reproduce ReadFile API calls of 1 byte? Two ways I know of, I didn't investigate any further: A) In Windows Explorer, click once on (i.e., select) any ODS or ODT file stored in a Dokan based filesystem (I suggest mirrorFS, it comes as an example with Dokan). I guess some sort of Explorer plugin loads parts of the file for meta information like author etc.; some 1-byte reads here. Normally (i.e., on NTFS or network shares), this doesn't hurt, but with Dokan it takes a LONG time to finish and bad things (like the filesystem software crashing) sometimes happen, but not always. B) Double-click on any ODS or ODT file stored in a Dokan based filesystem in order to load it, LOTS of 1-byte reads here while the file is being loaded, the filesystem virtually ALWAYS crashes. What are 'read' system calls and how they are related to LO? Ok, you got me there, normally I'm more of a POSIX programmer; from my perspective, read under POSIX does more or less exactly what ReadFile under Windows does, so I accidentally used the wrong name here, sorry for that, my bad. Of course I meant ReadFile system call. As to how they are related to LibreOffice, I can only imagine that LibreOffice will at some point through some means (probably hidden in some libraries) SPECIFIC TO LibreOffice and ODF files (because the problem ONLY appears with LibreOffice and ONLY with ODF files, see further down) do a series of ReadFile calls in order to read and interpret the ODS and ODT files. Which file is read this way? Pick *any* ODT or ODS (and, though I didn't try to confirm, I just guess we may include ODP) file ANYWHERE inside a Dokan based filesystem. No matter how large or small, what contents, it (by double-clicking in Explorer) always leads to huge amounts of 1-byte reads. All other file types I tried (doc, xls, txt, pdf, png, jpg, avi... I just clicked EVERYTHING I found) are working fine. In the meantime, I tested OpenOffice 4.0.1 in the same environment (i.e., I uninstalled LibreOffice and installed OpenOffice 4.0.1 on one of the machines - for now). I got no problems loading exactly the same files with OpenOffice that crashed Dokan with LibreOffice, so I think we can safely assume that the problem is specific to LibreOffice and ODF files. BTW, I am aware that just confirming this issue already means an extra lot of work while bringing next to no benefit, because of the special environment required (Dokan) and the comparably small number of people that are likely to be ever concerned by it. -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
[Libreoffice-bugs] [Bug 70224] LibreOffice 1-byte disk reads
https://bugs.freedesktop.org/show_bug.cgi?id=70224 --- Comment #1 from Urmas davian...@gmail.com --- I cannot reproduce it. Both ODT file, TEMP\.tmp file and PROFILE\.tmp file are read/written in 4K blocks. Can it be reproduced with clean profile, without JWM, etc? -- You are receiving this mail because: You are the assignee for the bug. ___ Libreoffice-bugs mailing list Libreoffice-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
